An agent that edits eleven files at once creates a review problem that no diff viewer was designed for. You are not reading one change with a clear author and a clear intent — you are reading a fan-out, where the interesting hunk is the third one in the seventh file and everything around it is mechanical. Klarcode's new inline review is built for that shape of change.

Accept the change, not the changeset

Every hunk an agent proposes is now its own decision. Accept it, reject it, or edit it in place and accept your version instead. Nothing is written to your working tree until you say so, and rejecting a hunk does not throw away the run — the agent keeps the accepted parts and re-plans around the gap you left.

  • Hunk-level accept, reject, and edit-then-accept, from the keyboard.
  • Rejected hunks feed back into the plan instead of ending the run.
  • The whole review is one transaction: close it and your branch is untouched.
  • Every accepted hunk keeps a link to the reasoning that produced it.

The risky hunk goes first

Order matters more than completeness when there are two hundred lines to get through. Klarcode now sorts a review by consequence rather than by file path: changes that touch authentication, migrations, money, or anything with a test that has failed in the last thirty days are lifted to the top of the queue. Formatting and import reshuffles collapse into a single row you can approve in one keystroke.

The reviewer's scarce resource is attention, not time. Spending it in alphabetical order is the actual bug.

Klarcode engineering notes

Verified runs

When a run finishes, Klarcode reports what it actually proved rather than what it attempted. A verified run means the build passed, the goldens for every touched flow still match, and the repository's declared invariants held. A run that could not prove one of those says so, names the check, and links the output — it does not round itself up to green.

This is the first half of a longer piece of work. The second half — reviewing a change against the behaviour it was supposed to produce, rather than against the lines it happened to touch — is what we are building next.