| ▲ | jmull 6 days ago | |
The question is why… The purpose of an ide is to pull together the tools a developer needs to develop software… first, reading/navigating and writing code, next running and debugging code, then (potentially) a variety of other tools: profilers, doc browsers, etc… all into a unified UI. But coding agents seem to already be able to use the command line and mcp quite well to do this. So why mediate using these tools through an IDE (over a new protocol) rather than just using the tools directly through the command line or mcp? It’s two extra levels of indirection, so there needs to be a really good reason to do it. There may very well be some actual problem this solves, but I don’t know what it is. | ||
| ▲ | lyu07282 6 days ago | parent [-] | |
> So why mediate using these tools through an IDE (over a new protocol) rather than just using the tools directly through the command line or mcp The IDE is in-between because it asks the user for confirmation before doing anything, if that's what you are asking. It's not adding any indirection or something, this is just how coding agents talk to the IDE already, all this does is standardize the language they speak which would be a win for everybody. | ||