Every run ends in Review: a task, a proposal, a refine, a sync. Nothing waits for a button — the work is on disk (in the worktree, for tasks) — but nothing moves on until you decide, and everything can be undone to the state before the run.

Where the review is

• The Cockpit’s Live tab is the main surface. Under the task list it shows the run’s files with added/removed counts. Whole run | Step N toggles between the diff of the whole change so far and the diff of the one task you just ran.
• The editor banner and the task card say Review and offer the same actions.
• The Agent Log’s completion card sums the run up — Finished · 2. Search API · 04:12 — and lists the documents it changed for document runs. Review the changes and Open in cockpit take you to the diff.

Double-click a file in the tree to open the IDE’s diff viewer between the pre-run and post-run snapshots. The tree can be grouped by directory or module and shown inline (Display Options). For a document run — propose, refine — the same panel diffs proposal.md, the deltas and tasks.md against their pre-run versions.

Comment in the diff

The diff viewer accepts inline comments exactly like the editor: put the caret on a line (either side, or the unified view), click the gutter balloon, write, Shift+Enter. Comments made in a diff are attached to the file and line, so they show up in the Cockpit’s Comments tab and travel into the next refine with the quoted code.

Comment on everything that is wrong before you refine, not one thing at a time — a refine is a full agent turn, and the agent handles a list well.

The actions

Move on

Run the next task (▷ on its row, Run next step in the banner, or Run All). This keeps the result of the run under review and starts the next one; there is no separate accept step. For a document run, “moving on” is running the first task; for the last task, it is finishing the change.

Refine

The refine control on a task row opens a chooser:

• Refine Code — re-run this task with your comments as corrective feedback. tasks.md is not changed; the code is.
• Refine Plan and Code — first revise this section of tasks.md from your comments, then re-run the revised section.
• Rollback Code and Refine Plan — roll the task’s code back to the pre-run state, then revise the section. Nothing runs; you run it again when the plan is right. Offered only where Rollback is (see below).

For a proposal or an earlier refine, the header offers Refine Spec: revise the documents from your comments, code untouched.

Refine is a new agent run and gets its own review. Comments go with it — all of them, or the ones you pick in the comment submit tab, depending on the Submit review comments automatically setting. Once sent, comments are cleared from the pending list; the History tab keeps them with the revision.

Refine is available on any completed task, not just the last one. Re-doing task 1 after task 3 is fine — the agent works on the current code and the diff shows what changed.

Rollback

Rollback restores the task’s files to their pre-run snapshot and puts the task back to Pending. It is offered only on the last completed task: undoing task 1 with tasks 2 and 3 built on top of it would leave the code in a state no run ever produced. To go further back, roll back one task at a time.

Rollback works after the session is gone — after an IDE restart, or a week later — because it uses the snapshots recorded in the run history, not anything in memory.

Stop, and what happens after

Stop in the Cockpit or the Agent Log cancels the agent’s current turn. For a task, the run is recorded as Interrupted: whatever the agent had already written is on disk, the row offers Resume (continue from where it stopped) and the usual Rollback. The agent conversation itself stays open, so you can tell it in chat why you stopped before resuming. See The Agent Log.

A run that ends in an error is Failed; the row offers Continue, which asks the agent to finish the section from its current state.

Viewed or not

The Spec Explorer marks a change whose review you have not opened yet with an accented icon; opening the log or the Cockpit review mutes it. With several changes running in parallel, that is how you see which ones need you.

What review does not do

Review never modifies your main working tree. For a task run in a worktree, the files under review are the worktree’s; your branch sees them only when you merge. For a run in the current branch (if you chose that), the files are already yours — Rollback is the undo.