← Back to context

Comment by lunarcave

1 day ago

Strictly speaking about large, complex, sprawling codebases, I don't think you can beat the experience that an IDE + coding agent brings with a terminal-based coding agent.

Auto-regressive nature of these things mean that errors accumulate, and IDEs are well placed to give that observability to the human, than a coding agent. I can course correct more easily in an IDE with clear diffs, coding navigation, than following a terminal timeline.

You can view and navigate the diffs made by the terminal agent in your IDE in realtime, just like Cursor, as well as commit, revert, etc. That’s really all the “integration” you need.

> I don't think you can beat the experience that an IDE + coding agent brings with a terminal-based coding agent.

CC has some integration with VSC it is not all or nothing.

  • Honestly, I think the Claude Code integration in VS Code is very close to the « nothing » part of the spectrum!

> I don't think you can beat the experience that an IDE + coding agent brings with a terminal-based coding agent.

I resisted moving from Roo in VS Code to CC for this reason, and then tried it for a day, and didn't go back.