Repository navigation
[FEATURE] Dart/Flutter Support #790
Description
Activity
- added 7 commits that reference this issue
on Oct 9, 2026 M1 (Dart) merged in #880. On
mainnow, unreleased:create_debug_session { language: "dart" }— the debugger is the SDK's owndart debug_adapter, run from whatever Dart or Flutter SDK is on the machine (DART_SDK/FLUTTER_ROOT, fvm pins, PATH); nothing vendored.- Launch a Dart program or a
package:testfile (args: ["-n", "test name"]picks one case); breakpoints, conditions, logpoints, stepping, variables, evaluate, exception filters,stopOnEntry,noDebug, exit codes. - Attach by
vmServiceUriorvmServiceInfoFile(never by PID), including a target started with--pause_isolates_on_start; detach leaves it running. - The Docker image carries the Dart SDK.
- Guide:
docs/dart/README.md; the measured facts behind it:docs/dart/spike-notes.md.
Next, as separate PRs: M2 = Flutter desktop/web and
flutter test/integration_test(the runner selection,deviceId, Windowsflutter.batbypass and warm-cache check are already in, awaiting their e2e coverage); M3 = Android emulators and devices, which is the "pass the device to use" part of this request, measured in the spike (-d emulator-5554,integration_teston the emulator, breakpoints in the app under test).Follow-ups filed from the work so far: #876 (hot reload / hot restart tool), #877 (
list_devices), #879 (Dart'sstep_overstops once per token position).- added 4 commits that reference this issue
on Oct 9, 2026 All three milestones are on
main, unreleased: #880 (M1, Dart), #881 (M2, Flutter desktop and tests), #883 (M3, Android emulator).What an agent can do with
language: "dart"now, each measured through the server (docs/dart/spike-notes.mdhas the numbers):- Dart programs and
dart testcases: breakpoints, conditions, logpoints, stepping, variables, evaluate, exception filters,stopOnEntry,noDebug, exit codes; attach by VM-service URI or service-info file. - Flutter widget tests (
flutter test,--namepicks one),integration_testfiles, andflutter runon a desktop device or an Android emulator —deviceIdis the-dvalueflutter devicesprints (windows,emulator-5554, a device serial). A breakpoint in the app code hits when an integration test drives it, which was the request here. - A Flutter launch answers
pending: truewhile the tool builds;wait_for_stopcollects the first stop (widget test ~6 s warm, desktop ~20 s, emulator ~21 s; a fresh project's first launch ~30 s, a cold Gradle build minutes).flutter test/flutter runsessions end without an exit code (the SDK adapter sendsterminatedonly); the✓ namelines are inget_output.
Guide:
docs/dart/README.md. Quirks: the Dart section ofdocs/KNOWN_ISSUES.md.Not yet: attaching to an app another
flutter runstarted on an emulator (#882), hot reload/restart as a tool (#876),list_devices(#877), web targets (listed byflutter devices, not exercised), physical devices (same path as the emulator, no device measured). Closing this issue with the three PRs; the follow-ups have their own numbers.- Dart programs and
- added a commit that references this issue
on Oct 9, 2026
🚀 Feature Request
Is your feature request related to a problem?
I would like to be able to get grok build etc. to debug dart/flutter apps just like I can with my C# backend.
Describe the solution you'd like
Please add dart/flutter debugging support with the ability to pass the head to use in.
Describe alternatives you've considered
Using vs code with debugmcp and the flutter extension debugger.
💡 Use Case
I want to be able to do e2e tests with great debug breakpoints and pulling variable values etc..
📊 Impact
🤝 Are you willing to contribute?