Review & land
Nothing reaches your tree until you have read the diff.
An agent's work sits on its own branch until you land it. The review panel shows every changed file, every hunk, the tests it ran, and two buttons.
- Split or unifiedthe diff reader you already know, with comments
- Land or discardone button each; nothing lands by surprise
- Conflicts surfaceas an Attention card, with the agent offered the resolve
The review boundary is a real branch
Landing replays the agent's delta onto your tree as ordinary git changes you can stage, amend or revert. Discarding removes the worktree and leaves your tree untouched.
One base commit, one branch each
land, one at a time, after you have read the diff
Your working tree
untouched until you land, and still yours to amend or revert afterwards
Reviewed by file, not by wall of text
Files are grouped by repo with their line counts, so a 400-line change reads as six decisions. Comments attach to a hunk, and unread files stay marked until you have looked at them.
A conflict is a task, not a dead end
When a land collides with work that arrived first, the card moves to Attention and the agent offers to resolve it in its own worktree.