REVIEW mode

§ REVIEW

REVIEW is where you see exactly what changed and decide what stays. It is a diff viewer, a code editor, a test runner, and an AI reviewer in one surface — so you can read a change, fix it in place, run the tests, and ship it without leaving the mode.

How to open it

Press ⌘⇧3, or click Review in the mode switcher. REVIEW is always present in every workspace.

[screenshot: REVIEW mode showing a unified diff with per-hunk controls]

The interface

Diff view. Toggle between unified and split layouts. Each file can be collapsed to keep long diffs navigable, and a whitespace-ignore toggle hides noise from reindentation.

Per-hunk Accept / Reject. Work hunk by hunk. Accept what you want to keep; reject what you don’t. A reject is reversible — there’s an undo if you change your mind.

Embedded editor. REVIEW ships an integrated CodeMirror editor with syntax highlighting for JavaScript, TypeScript, Python, Rust, Java, CSS, HTML, XML, YAML, JSON, and Markdown. Edit the file right in the diff surface — no round trip to another tool.

Test runner. Each workspace can define a custom test command. Run it from REVIEW and see the result inline, so you can confirm a change before you accept it.

AI Review. Ask a model to review the diff. Findings come back deep-linked to the exact file and line, with a cost estimate for the review itself. If you keep editing after a review, Octopush detects that the findings are stale and offers to re-run.

The Companion panel shows the changed-files tree and a commit box. Git state is tracked here too: status polling, ahead/behind counts, and an open-PR chip surfaced via the gh CLI when a pull request exists for the branch.

A typical flow

1. After the agent makes changes, press ⌘⇧3.
2. Skim the changed-files tree in the Companion; switch to split view if the change is large.
3. Walk the hunks: Accept the good ones, Reject the rest. Undo a reject if needed.
4. Spot a small mistake? Fix it directly in the embedded editor.
5. Run the workspace test command and confirm it’s green.
6. Run AI Review and jump to each deep-linked finding to triage it.
7. Write a commit message in the Companion and commit. If a PR exists, the open-PR chip links to it.

Shortcuts

Shortcut	Action
⌘⇧3	Switch to REVIEW
⌘K	Command palette (editor toggles, theme)

Tips

Review, then re-review

AI Review is most useful as a second pass. Accept the obvious hunks first, then run AI Review on what remains. If you edit afterward, the stale-detection prompt reminds you the findings no longer match the diff.

Note

Whitespace-ignore only affects how the diff is displayed and reviewed — it doesn’t rewrite your file. Reindentation still lands in the commit unless you reject those hunks.

Caution

The open-PR chip relies on the gh CLI being installed and authenticated. Without it, Octopush can still show local git status and ahead/behind counts, but it can’t detect an existing pull request.