I am constantly surprised how seldom aider is mentioned in threads like this. I understand that it's not directly integrated into the editor, but the "editor + parallel CLI tool chain" paradigm feels so natural to me because we drop to terminal for so many other parts of building software. If you haven't tried it (particularly the architect/editor modality), it's worth a couple of hours of experimenting.
Aider doesn’t provide any interface that’s integrated into the editor tool, as you point out. That might be true for other similar side-by-side tools that I am not aware of.
But, if you tell aider to watch your files, you can drop a specially formatted comment into your file, and aider will see that and use it as a prompt.
So the integration is sort of “implicit”. Which sounds kinda like the cheap way to go, in comparison to the current brand name tools that have their own chat boxes, dropdowns with mode selectors (ask, edit, agent), and so on.
But look further into the future and an ambient interface is probably where we end up. Something where the Ai agent is just watching what you do, maybe even watching your eyes and seeing what you’re attending to, and then harmonizing its attention to what you are attending to.
Tight editor integration means better diffs (right in your editor), easier context manager, and other convenience features that CLI-only tools can't have.
This doesn't mean that aider, claude code, etc. aren't very good tools, but it does make sense to distinguish between built-in tools vs external ones. A similar non-AI example is debugging or linting: IDE integration makes it much easier than using a separate tool.
