> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plannotator.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Local Diff Review for Coding Agents

> Open local code changes in Plannotator, add line-specific comments or suggestions, and send structured feedback back to your coding agent.

Run `plannotator review` in a repository to inspect the current change set in a browser. Plannotator shows a file-oriented diff, lets you comment on exact lines or ranges, and returns the review to the agent session as structured feedback.

*Originally published February 19, 2026, by backnotprop. Last reviewed July 18, 2026. Maintained by the Plannotator project.*

## Start a local review

```bash theme={null}
plannotator review
```

Most supported agents also install a review command or skill. For example, Claude Code uses `/plannotator-review`, while Codex can use `$plannotator-review` or `!plannotator review`.

Plannotator detects the repository and builds the opening review from the current VCS state. For Git, the default `since-base` view includes committed branch work, working-tree changes, and untracked files when the base branch resolves. If no base resolves, Plannotator falls back to uncommitted work instead of hiding committed changes.

The [original Plannotator demo](https://www.youtube.com/watch?v=a_AT7cEN_9I) shows the browser review loop. The current UI has expanded since that recording, so use the documentation below for present behavior.

The Git status panel separates the result into **Committed**, **Changes**, and **Untracked**. You can switch to the file tree, change the comparison, or open the session-only commit history where the repository supports it.

## Add precise feedback

Select one line or a range in the diff, then add a comment or suggested replacement. Plannotator keeps the file path, line range, and diff side with the annotation.

When you select **Send Feedback**, the agent receives a Markdown review grouped by file. A typical item identifies the file, selected line, comment, and suggested code. The agent can act on that review without reconstructing your intent from a general chat message.

Use **Approve** when the change is ready. Plannotator returns the configured code-review approval message to the active agent session. It does not commit, merge, or deploy the change.

## Stage and unstage carefully

Local Git reviews can stage or unstage supported files from the review UI. That control does not apply to every VCS provider or review mode. Do not expect it for Jujutsu, Perforce, remote-only pull request diffs, or already committed files.

## What stays local

For a local review, Plannotator starts a temporary server on `127.0.0.1` and reads the diff from the local repository. The patch is served to your browser on the same machine. Optional features can make external requests, including Ask AI, remote assets, or commands you explicitly run, but the basic local diff review does not upload the patch to a hosted Plannotator service.

## When local diff review helps

Use it when an agent changed several files, the terminal diff is hard to navigate, or your feedback needs exact line context. Repeat the review after the agent responds so you can verify the current code instead of approving from its summary.

<Card title="Review code with Plannotator" icon="code-compare" href="/open-source/workflows/local-changes" arrow="true">
  Learn the local, pull request, merge request, VCS, and provider boundaries.
</Card>