Code review in the editor

Review the run's branch with native diffs and inline comments — submitted as one rework, whenever you like.

Gate notes are fine for "looks good" or one paragraph of direction. When you want to review the actual diff, line by line, use the editor's native code review.

Start a review

Click Review changes in the live session (it appears once the run has commits), or right-click the run in the Runs panel. Peractor fetches the run's branch into a hidden ref and diffs it locally — nothing is checked out, your working tree stays untouched.

Comment on the diff

A Review changes view lists every changed file — flat or as a tree, with Open All Changes to stack them in the multi-file diff editor. Add inline comments with the native "+" gutter, exactly like reviewing a pull request. Agent edits shown in the transcript open into the same native diffs, gutter and all.

Submit

Submit Review bundles all comments into one "request changes". You can do this at any moment in the run's life:

• Run parked at a gate — the rework starts immediately.
• Run still working — the review is queued and applies automatically the next time a phase parks.
• Run already finished — the final phase re-opens as a continuation and applies your notes to the finished branch.

Reviews are attributed to your signed-in identity and honor the phase's approver policy, so a code review carries the same authority as a gate decision.