Repository navigation
Feature Request: Please add flutter/dart to the fully supported list #126
Description
Right now it appears to work to a certain extent. But I'm not sure it's fully working because the AI has a ton of trouble with it:
- AIs can't figure out that a session is already running properly
- They can't seem to start a session reliably (because they take a long time to start a head). It's as if they can't get the status of starting the session and because they can't read the debug console in vs code, they can see that it's still starting. (not sure why vs code doesn't allow reading the debug console!).
- Once they get into a session they often fail to use the tooling effectively although they confirm that they have access to the mcp and can use the tools.
I'm not sure that 1 and 2 aren't a global improvement to the mcp that couldn't be made to give status and lookup existing sessions and teach them how to do this before they start another debug session, but it sure rears it's head on flutter more than C#. And adding access to the debug console here would be hugely powerful because with flutter, this is where inline errors that don't get trapped on code execution go.
I'm happy to do testing and feedback on this.
Thanks!
Activity
ozzafar commentedon Sep 9, 2026
Thanks for the detailed report and for offering to test!
Could you retry with DebugMCP 2.3.4 (or newer)? Version 2.3.4 introduced
get_debug_status, which reports whether the active debug session is running, paused, or absent without changing execution state. It also includes improvements for attaching to long-running processes and returning promptly after continue. These may address some of the session-awareness problems, but we haven't confirmed that they resolve Flutter startup or tooling reliability.If you still encounter problems, please share:
launch.jsonand any relatedtasks.jsonconfiguration.get_debug_statusbefore starting a session and after the problem occurs.Please also let us know whether starting the same configuration manually in VS Code works and roughly how long startup takes. Debug-console access is a separate gap; the new status tool does not expose that output.
JohnGalt1717 commentedon Sep 30, 2026
It works about 50% of the time. It still fights multiple open vs code windows not working right (this should be embedded into vs code and not a separate server!) and the AI goes off the rails not understanding how to use it properly on a regular basis.
But it is better than it was.