get_problems and get_terminal as tools #3451
Replies: 2 comments
-
hey folks, i hope i am not spamming threads. i wanted to understand why this isn't a bigger problem to the community? Is it because a lot of us use iterm2 or some other terminal mcp servers? Piping output seems like a problem that other IDEs haven't solved well, so i do not mean to be very expectant about it. But I do not feel comfortable creating long term workflows where something as key as observability of running terminal commands is achieved with mcp servers. |
Beta Was this translation helpful? Give feedback.
-
Correcting myself here since i saw augment code notice that an api server had started with errors, even though terminal had not exit yet. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
@Terminal and @problems mentions are very useful, but they are only processed in manual prompts. It would be good if Roo can call these tools anytime when needed, e.g. according to instruction files in .roo/*
The same idea is valid for other VScode content and tools, e.g. see https://github.com/biegehydra/BifrostMCP
Beta Was this translation helpful? Give feedback.
All reactions