Add PR-style review comments in Git Diff UI that feed into the active agent thread
### Discussed in https://github.com/zed-industries/zed/discussions/54663 <div type='discussions-op-text'> <sup>Originally posted by **GoodnessDev** April 23, 2026</sup> # What are you proposing? I am proposing PR-style review comments directly in Zed's Git Diff UI, where human comments on a file, hunk, or line get fed into the currently active agent thread as structured feedback. This is not the same as "attach the current diff to the thread" or "ask AI to review the diff". The key workflow is the other direction: 1. I review the local diff in Zed's Git UI. 2. I leave one or more targeted comments, like I would on a GitHub PR. 3. Those comments are sent into the active agent session/thread. 4. The agent can respond to the comments and make follow-up edits. Example: - I open a Git diff in Zed. - On a hunk, I leave a comment: `This rename breaks the public API. Keep the old name and add an overload instead.` - That comment becomes a new message or structured feedback event in the active agent thread, with the relevant file/hunk context attached. - The agent then addresses that exact review feedback. # Why does this matter? Right now, Zed has good ingredients, but the feedback loop is still weak: - the Git UI shows diffs - the Agent Panel can edit code - `Review Changes` exists for agent edits - checkpoints exist per message But there is no first-class way to do what many of us already do on GitHub PRs: - inspect a diff visually - leave precise review comments on a spe
Posted by macraig on Jun 11, 2026, 9:30 PM
Tags
Related issues
- This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
- I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
- the new VSCode UI, looks cute, i don't like it.
- I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
- The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
- Thanks for indulging me so far, by the way, I really appreciate this discussion, it's very stimulating.
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
ux (Software)
This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
the new VSCode UI, looks cute, i don't like it.
I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
Add PR-style review comments in Git Diff UI that feed into the active agent thread
Thanks for indulging me so far, by the way, I really appreciate this discussion, it's very stimulating.
Migrate GDScript to the GDExtension mechanism and overhaul the implementation
Add PR-style review comments in Git Diff UI that feed into the active agent thread
### Discussed in https://github.com/zed-industries/zed/discussions/54663 <div type='discussions-op-text'> <sup>Originally posted by **GoodnessDev** April 23, 2026</sup> # What are you proposing? I am proposing PR-style review comments directly in Zed's Git Diff UI, where human comments on a file, hunk, or line get fed into the currently active agent thread as structured feedback. This is not the same as "attach the current diff to the thread" or "ask AI to review the diff". The key workflow is the other direction: 1. I review the local diff in Zed's Git UI. 2. I leave one or more targeted comments, like I would on a GitHub PR. 3. Those comments are sent into the active agent session/thread. 4. The agent can respond to the comments and make follow-up edits. Example: - I open a Git diff in Zed. - On a hunk, I leave a comment: `This rename breaks the public API. Keep the old name and add an overload instead.` - That comment becomes a new message or structured feedback event in the active agent thread, with the relevant file/hunk context attached. - The agent then addresses that exact review feedback. # Why does this matter? Right now, Zed has good ingredients, but the feedback loop is still weak: - the Git UI shows diffs - the Agent Panel can edit code - `Review Changes` exists for agent edits - checkpoints exist per message But there is no first-class way to do what many of us already do on GitHub PRs: - inspect a diff visually - leave precise review comments on a spe
Comments (0)
No comments yet. Start the discussion.