agent-manager

Docs · Diff review

Diff review

ctrl+r on a session opens a full-screen review of its repo: changed files with +/− counts on the left, the whole file on the right with syntax highlighting and changed lines tinted, so every edit reads in full context. The diff refreshes as the agent keeps editing.

Fig. 3ctrl+r · review
Animated demo of the review screen: scrolling a changed Go file side by side with the original, then jumping to the next changed file.

Comments go back to the agent

c writes a note on any line and d drops one. Comments stay on the review screen until you send them: C flattens every one into a single prompt, asks you to confirm, and delivers it into the agent's pane, so the agent starts addressing your notes while you watch the diff update.

Keys

KeyAction
↑↓ / j kScroll the file. ctrl+d and ctrl+u move half a page, g and G jump to the ends.
J / KPrevious and next file. tab and shift+tab do the same.
n / NJump between changes.
uToggle unified and side by side, holding the cursor on the same source line.
sCycle the scope: uncommitted, versus target, last commit, staged.
rPick the repo when the session's directory holds several. Type to filter.
bPick the branch from the repo's worktrees.
BPick the target the "versus target" scope compares against.
spaceMark a file reviewed.
c / dWrite, drop a line comment.
CSend every comment to the agent as one review prompt.
esc / qClose the review.

Each changeable value in the header wears its own key, so the scope, layout, repo and target pills read as s, u, r, B legends at a glance.

Fig. 4side by side
The review screen, side by side, with changed lines tinted inside the full file.

Which repo it opens

A session's working directory is often an umbrella folder holding many repos, so review cannot simply guess. An agent that knows which repo it is in says so by calling the review_repo tool, or by running the subcommand from a shell inside its session:

Terminal
agent-manager review-repo /path/to/repo
agent-manager review-base main

The path is checked to be inside a git repo and resolved to the repo root, so a declaration is a fact rather than a guess. Review then resolves its target in a fixed order:

Worktrees Linked worktrees are discovered wherever they live on disk, so one declaration names both the repo and the branch under review. A stored base ref that stops resolving surfaces as an error in review, and B opens a picker to set or clear it.