Diffsmith - Comment on your AI agent's code & collaborate on changes

honestly this looks really useful for reviewing ai-generated code, the per-line commenting with mcp replies is a clever touch. one thing that would help me a lot is a way to filter the diff to only show files changed by the agent versus my own edits, so i can focus the review where it matters most. sort of a split view toggle.

A diff view that groups related changed lines into collapsible logical blocks (function, class, block) would be huge when reviewing large AI-generated changes, instead of scrolling through every single line individually. Would love to see something like that next.

Would love to see a way to group comments into review rounds so I can do a first pass, send notes to the agent, then do a follow-up review on just the changed lines from the next commit without losing my original feedback.

A diff view that groups changes by file with a quick-jump sidebar would save a lot of scrolling on larger branches, especially when I'm bouncing between several modified files at once.

Would love to see a way to filter or group comments by the agent that generated the diff. When I'm reviewing changes from both Claude Code and Cursor in the same session, it gets hard to track which feedback needs to go back to which tool. A simple dropdown to view only comments for a specific agent's changes would save me a lot of mental overhead.

Finally a clean way to review what my AI agent just churned out without scrolling through terminal output. Clicking a line to leave a note and bouncing it back through MCP feels exactly like the workflow I didn't know I needed.

One thing I'd love to see is a keyboard shortcut to jump between comments during review, something like cmd+] and cmd+[ to cycle through them. Right now clicking around to find each note breaks my flow when I'm going through a big diff.

The MCP path is what makes this a loop rather than a one-way review, since the agent's replies land back at the line they belong to. Where does that comment state actually live: inside the repo as something I would gitignore, or in app-local storage outside the working tree? I ask because I want to know what happens to anchored comments when I switch branches or stash mid-review, and whether the MCP server is something the agent polls for new notes or you push to it when I finish a pass.

finally a way to actually talk back to my AI agent line by line instead of copy pasting diff hunks into chat. The MCP reply viewer at the exact line of code is genuinely useful.

the archiving-on-rewrite answer above covers the case where the agent edits a commented line. curious about the other trigger though: if the agent just runs `git commit` mid-session, does Diffsmith diff against the new HEAD and archive everything the same way, or does it lose track since it was anchored to the previously-uncommitted state?