Code review
Review the actual diff line by line, from your editor, a browser, the Mac, or your phone.
A gate note is fine for "looks good" or a paragraph of direction. When you want to review the diff itself, line by line, Peractor has a proper review on every surface.
Start a review
Open Review changes on a run — it appears once the run has commits. Peractor fetches the run's branch and diffs it. In the editor, nothing is checked out and your working tree is untouched.
Comment on the diff
You get every changed file, as a flat list or a tree, and a diff for each one. Add a comment on any line.
| Part of a comment | What it means |
|---|---|
| The line, and its side | A removed line 6 and an added line 6 are two different lines. A comment is anchored to both. |
| Text | What you want to say. |
| Attachments | Files belong to the comment, not the review — the screenshot sits with the remark it illustrates. The agent gets them staged into its workspace with the paths named under your note. |
There is also a review summary: a comment about the whole change rather than any one line, reached from the review screen's menu. It leads the note the agent receives.
Per surface
- Editor — a native Review changes tree, the editor's own "+" gutter for comments, and Open all changes to stack them in the multi-file diff editor. Agent edits in the transcript open into the same native diffs.
- Browser and desktop — the diff opens as a sheet from the run, per edit or across the whole branch, with the comment box inline.
- Mac — the same review in a window of its own, beside the transcript.
- iPhone and Android — the full review, with per-line comments and attachments. Leaving a review with unsent comments asks first.
Submit
Submit review bundles every comment into one "request changes". You can do this at any point in a run's life:
- Parked at a gate — the rework starts immediately.
- Still working — the review is queued and applies automatically the next time a phase parks.
- 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 honour the phase's approver policy, so a code review carries the same authority as a gate decision.
Opening a file where you work
From a run's changed file, Open in… opens it at its first changed line in the editor you actually use — VS Code and its forks, JetBrains, Xcode, Zed, and a dozen others. The picker lists what is installed and remembers your choice.