# Reviewing changes

Source: https://cohalen.com/docs/review



When a turn ends, you read what it did. **Review** shows the workspace's
changeset: every file the task touched, measured against the base branch.

That's the same set of files the pull request will contain, and you read it as one
thing.

## The Review tab [#the-review-tab]

Every changed file renders as a collapsible section in one continuous scroll. The
**Outline** on the left lists those files with the diffstat and jumps you to any of
them. The body always holds the whole changeset, so nothing hides behind a file
switcher.

Mark a file **Reviewed** once you've vetted it. Its section collapses and dims, and
the outline counts how far you've got. Reviewed is your own tracking, not a git
operation.

## Notes: feedback the agent acts on [#notes-feedback-the-agent-acts-on]

A note is a comment on a diff line written for the agent, not for another person.
Mark it `critical`, `suggestion`, or `question`.

Notes carry the exact file and line into the agent's next turn. That's what makes
them the precise way to ask for a fix. Instead of describing where the problem is,
you point at it.

## Quick edits in the Editor [#quick-edits-in-the-editor]

When prompting is slower than typing, the **Editor** opens any file in the
workspace's worktree. A file tree, quick-open by path, one file at a time. Type a
path that doesn't exist and it offers to create it.

A buffer touches disk only when you save, and a saved edit or a new file joins the
changeset like any other change. The Editor opens, creates, and edits files. It
doesn't rename, move, or delete them.

When one line isn't 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.