Review diffs, comment, send back

microManager shows every change in a workspace as a diff against the branch you will merge into, untracked files included. Click a line number to comment, then send your comments to the agent, which reads them and makes the fixes in the same chat.

Updated

The diff of src/app.ts in the Branch view, with the new GET /transfers route highlighted and a line comment under it asking for a ?limit= parameter, a Send 1 to agent button, and the Changes panel listing accounts.ts, app.ts and app.test.ts with the lines each added.
Comment on lines of a diff, then send the comments to the agent.

What does the Changes panel show?

Every file the workspace changed, as a tree, each with its status (added, modified, deleted, renamed) and its added and removed line counts. A toggle switches between two views:

View Compares Good for
Branch The merge base with the target branch, against the working tree, plus untracked files Reviewing the whole task before a pull request
Uncommitted The last commit against the working tree Checking what the agent did in the last turn

⌘⇧E (Ctrl+Shift+E on Windows and Linux) shows or hides the panel.

How do I read a diff?

Click a file to open its diff over the chat, or beside it. Choose unified or split view; both have syntax highlighting.

How do comments get back to the agent?

Click a line number to comment on that line, or Shift-click or drag across line numbers to comment on a range. Comments collect in the Review panel. When you are done, Send to agent (it counts them: Send 2 to agent) sends every open comment to the chat tab on screen as one message, each with its file and lines, and the agent works through them. Sent comments are marked Sent, and you can resolve them once fixed, or reopen them.

Can agents leave comments too?

Yes. Through microManager’s MCP server, an agent can call GetWorkspaceDiff to read the workspace’s changes, DiffComment to leave comments on specific lines and GetDiffComments to read the comments not resolved yet, so “address my comments” works without sending them. Ask one agent to review what another wrote, and its findings land in the same Review panel as yours. See MCP tools.

What if I do not like what the agent did?

Roll the workspace back to before the message that caused it with a checkpoint, or tell the agent what to change. When the diff looks right, open a pull request.

Where to go next

Frequently asked questions

Does the diff include files the agent has not committed?

Yes. The branch view compares the merge base with the target branch against the working tree, so committed, uncommitted and untracked files all appear. The uncommitted view shows only what changed since the last commit.

Can an agent review another agent's work?

Yes. Agents can read the diff with the GetWorkspaceDiff tool, leave line comments with the DiffComment tool and read yours with the GetDiffComments tool. Their comments appear in the Review panel next to yours.

Is there a limit on file size?

Each file's diff is capped at 1 MB and marked as truncated beyond that, so one huge generated file cannot freeze the view. Binary files are listed without a diff.

Get microManager

Free, no account, for macOS, Windows and Linux. It runs the agent CLIs you already have installed and signed in.

curl -fsSL https://micromanager.win/install.sh | sh

That installs it on macOS and Linux. On Windows, paste this into PowerShell:

irm https://micromanager.win/install.ps1 | iex