dart-hot-reload
To apply latest code changes to a running Flutter app, trigger hot reload after connecting to the Dart Tooling Daemon.
When & Why to Use This Skill
The Dart Hot Reload skill enables developers to instantly apply code changes to a running Flutter application by interfacing with the Dart Tooling Daemon. This tool streamlines the development workflow by allowing real-time updates without losing the application's current state, significantly reducing the feedback loop during mobile and web app development.
Use Cases
- Rapid UI Iteration: Instantly preview changes to Flutter widgets, layouts, and styling during a live coding session to achieve pixel-perfect designs without restarting the app.
- Stateful Debugging: Fix logic errors or update functions and apply the changes immediately while maintaining the current navigation stack and user data.
- Error Recovery: Use the clearRuntimeErrors feature to reset the application's error state after applying a fix, ensuring a clean environment for continued testing.
| name | dart-hot-reload |
|---|---|
| description | "To apply latest code changes to a running Flutter app, trigger hot reload 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":"hot_reload","arguments":{}}
Tool Description
Performs a hot reload of the active Flutter application. This is to apply the latest code changes to the running 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 runtime errors before hot reloading.",
"description": "This is useful to clear out old errors that may no longer be relevant."
}
},
"required": []
}
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>"}}