Review agent changes

The Review tab answers the only question that matters after an agent run: what did it actually do? It shows the workspace’s total change against the base branch — committed, staged, unstaged, and untracked, all in one list — so nothing the agent did can hide in a commit you didn’t open. It’s part of how AI in Birch keeps the human in the loop.

What the Review tab shows

Review is the fourth sub-tab of the workspace’s Git tab (Changes · History · Stash · Review). Where Changes shows only uncommitted work, Review diffs the whole worktree against its base branch: every commit the agent made plus everything still staged, unstaged, or untracked. The header sums it up — vs {base} — {n} commits, {m} files — and an untouched workspace shows “No changes vs the base branch yet.”

If the base branch can’t be found (for example, it was deleted), the tab falls back to “Base branch ‘{base}’ not found — showing uncommitted changes only ({m} files)”.

Note

The Review tab exists only on non-primary worktrees — agent workspaces and extra worktrees. The repository’s primary checkout has no base branch to diff against, so it shows Changes, History, and Stash only.

Getting there

• Automatically — when a workspace’s last terminal exits, the panel lands on the Review tab. Finish an agent run, and the audit is already open. That’s the intended habit: review first, then ship.
• Review changes in the workspace properties panel, or its {N} files vs {base} changed-files card.
• Manually — the workspace’s Git tab, then the Review sub-tab.

Walking the changes

Select a file in the list to read its diff — unified or side-by-side, with optional whitespace-ignoring and word-level highlighting; see Reading diffs for the full tour. The change-count badges — on the Git tab button and on the sidebar workspace row — show the same files-vs-base number, so you can gauge how big an agent’s change is before opening it at all.

Fixing up agent work

Review is for reading; corrections happen on the Changes tab:

• Uncommitted work can be discarded per file (row context menu) or per hunk (the discard strip on an unstaged file’s diff).
• Commit fixes on top of the agent’s commits — or amend the last one — as usual; see Commit changes.

Handing off

Once the diff reads clean, Create PR (in the properties panel or the Git tab’s toolbar) opens the create-PR dialog prefilled from the agent’s session title and the branch’s own commits — see Create a pull request.