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!
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:
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!