Every editor now reviews your agent's code. Where do your comments go?
The big editors all have an agent built in now, and each of them has added a way to look at what the agent did before you keep it. I build Reado , the IDE for reading the code your agent writes, so I have an obvious interest in this question. That's exactly why I went through each tool's own documentation instead of my memory of it. Everything below links to the vendor's page. The full…
Each of the major code editors now includes an agent, offering a way to review the changes made by the agent before they are committed. Reado, the IDE for reading the code written by the agent, provides an obvious solution to this problem. To learn more about the various options, you can refer to the vendor's pages for each tool. The comparison page offers a side-by-side overview of the tools, which is free and open source.
When an editor lets you view the agent's changes and accept or reject them, there are differences in how the workflow is handled. VS Code allows you to keep or undo each inline change in a local session, while Agent Host sessions don't have that granularity; instead, you mark files as reviewed. Zed opens a Review Changes tab with every edit, where you can accept or reject each hunk or the entire set.
Cursor shows the agent's edits in a diff view, where you can reject changes with checkpoints to roll back. JetBrains allows you to open each file modified by the agent and roll back per file or everything at once.
After the changes are made, the question remains: where do your comments go? With an agent, comments need to be accessible to the agent and should still make sense even if the code has been moved around. The editors differ in their approach to handling comments. VS Code stores comments in the Agents window, where they are resolved and disappear from the diff.
Zed's editor docs do not describe line comments for the agent, but they are building them in Delta, a separate product in private beta. Cursor has Agent Review and Bugbot for pull requests, which can be handed to a cloud agent to fix issues. Line comments you write yourself for the local agent are not mentioned in the docs. JetBrains Junie docs do not mention line comments at all.
When it comes to line comments for agents to resolve, the location of these comments varies. VS Code has a dedicated place for them, while Zed has a beta version called Zed Delta. Cursor's Bugbot findings can be fixed by an agent, but those are the reviewer's comments on a pull request, not yours. Tools like Orca, Warp, Diffsmith, and GitHub also offer different approaches to handling comments. Each tool has its own way of storing and managing comments, determining their fate after the code has been modified.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
