Reviewing changes
Read the Changeset in the Diff view, leave Notes the agent will act on, and make quick hand edits without leaving the Workspace.
When a Turn ends, the second stage of the workflow begins: review. The Diff view presents the Workspace's Changeset, the complete set of files the task changed measured against the Base branch, commits plus uncommitted edits. It is the same set of files the pull request will contain, reviewed as a whole.
The Diff view
Every changed file renders as a collapsible section in one continuous scroll. The Outline on the left lists the files with the aggregate diffstat and jumps to any of them; the body always shows the whole Changeset, so nothing is hidden behind a file switcher.
Mark a file Reviewed once you have vetted it: its section collapses and dims, and the Outline counts progress (1 of 3 reviewed, and so on). Reviewed is your own review-tracking state, not a git operation.
Notes: feedback the agent acts on
A Note is a comment on a diff line whose audience is the agent, not a
human reviewer. Mark it critical, suggestion, or question. Notes carry
the exact file and line into the agent's next Turn, which makes them the
precise way to request a fix: instead of describing where the problem is,
you point at it.
Quick edits in the Editor
For the fixes where prompting is slower than typing, the Editor opens any file in the Workspace's worktree: a file tree with quick-open by path, one file open at a time. Typing a path that does not exist offers to create the file. A buffer touches disk only on save, and a saved edit or a created file joins the Changeset like any other change. The Editor opens, creates, and edits files; it does not rename, move, or delete them.
When one line is not enough, Open in IDE hands the worktree to your external editor. The worktree is a real git checkout on disk, so anything you change there shows up in the Changeset too.
Next: Checks and Ship, from reviewed to merged.