Hunk-by-hunk review
Every diff is broken into hunks. Accept or reject each one.
What's a hunk
A hunk is a contiguous chunk of a unified diff — a block of additions/deletions with surrounding context. One file may have many hunks if changes are spread out.
Per-hunk controls
Each hunk header has two buttons:
- Accept — keep this hunk in the staged change.
- Reject — drop this hunk. The file's other hunks are unaffected.
Hunk state is shown by a colored side stripe:
- Green stripe = accepted.
- Red stripe = rejected.
- Neutral = undecided (default state).
Until you click Apply, no actual file mutation happens — you can flip decisions freely.
File-level shortcuts
Each file has its own header buttons:
- Accept all — accepts every hunk in this file.
- Reject all — rejects every hunk in this file.
Apply behavior
When you click Apply at the top of the Changes panel:
- Accepted hunks are applied.
- Rejected hunks are dropped from the diff.
- Undecided hunks default to accepted unless you've turned on "Default undecided to reject" in Settings.
A snapshot is taken first; a receipt is issued after.
Why hunk-level
Hunk-level review is the difference between "the agent did one good thing and one bad thing" and "I have to accept or reject the whole batch". You keep the good and drop the bad.
The cost: more clicks per run. The upside: much higher trust in what actually lands.
Tips
- Glance at the top of each diff first. If the file is short or every hunk looks reasonable, Accept all is fine.
- For large diffs, scroll through and only Reject the obvious problems — the rest defaults to accepted.
- If a hunk looks wrong but you're not sure, leave it undecided and ask the agent to explain.