dart-get-runtime-errors
To read recent runtime errors from a running Dart or Flutter app, fetch runtime errors after connecting to the Dart Tooling Daemon.
When & Why to Use This Skill
This Claude skill enables developers to seamlessly retrieve and monitor recent runtime errors from active Dart or Flutter applications. By interfacing with the Dart Tooling Daemon, it provides real-time insights into application exceptions and crashes, allowing for faster diagnostic cycles and improved code stability directly within the AI-assisted development workflow.
Use Cases
- Real-time Debugging: Quickly identify and diagnose UI crashes or state management exceptions in Flutter mobile apps during live development sessions.
- Error Log Management: Retrieve and clear runtime error buffers to maintain a clean debugging environment and focus on the most recent issues during iterative testing.
- Backend Monitoring: Monitor Dart server-side applications for unexpected runtime errors to ensure backend reliability and rapid bug resolution.
| name | dart-get-runtime-errors |
|---|---|
| description | "To read recent runtime errors from a running Dart or Flutter app, fetch runtime errors after connecting to the Dart Tooling Daemon." |
Usage
Use the MCP tool dev-swarm.request to send the payload as a JSON string:
{"server_id":"dart","tool_name":"get_runtime_errors","arguments":{}}
Tool Description
Retrieves the most recent runtime errors that have occurred in the active Dart or Flutter application. Requires "connect_dart_tooling_daemon" to be successfully called first.
Arguments Schema
The schema below describes the arguments object in the request payload.
{
"type": "object",
"properties": {
"clearRuntimeErrors": {
"type": "boolean",
"title": "Whether to clear the runtime errors after retrieving them.",
"description": "This is useful to clear out old errors that may no longer be relevant before reading them again."
}
}
}
Background Tasks
If the tool returns a task id, poll the task status via the MCP request tool:
{"server_id":"dart","method":"tasks/status","params":{"task_id":"<task_id>"}}