herdr-reviewr CLI
A herdr plugin: the agent's code diff in a terminal pane beside the chat, line comments and notes sent back to Claude Code, Codex or OpenCode
- 928 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Sees the whole git worktree, including files outside the diff, and launches your editor on a key press
- Pastes comments into the herdr agent's input, after which the agent acts by its own rules
- The PR tab talks to GitHub, GitLab or Azure DevOps through your signed-in `gh`, `glab` or `az`
Install
- Works in
Manual install
herdr plugin install persiyanov/herdr-reviewrPrebuilt binaries are installed, no Rust toolchain needed. Open the pane with `herdr plugin action invoke open --plugin persiyanov.reviewr`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Sees the whole git worktree, including files outside the diff, and launches your editor on a key press
- Pastes comments into the herdr agent's input, after which the agent acts by its own rules
- The PR tab talks to GitHub, GitLab or Azure DevOps through your signed-in `gh`, `glab` or `az`
This is third-party code. Review the repository files before installing.
What it does
herdr-reviewr opens the changes the agent made in a separate terminal pane with syntax highlighting. The pane is tied to a git worktree. The agent writes code, you read the diff beside its chat, select a line or a range with `v`, comment with `c`, and `s` sends all comments to the agent's input. `y` copies them to the clipboard. The diff opens in four scopes: uncommitted edits, the whole branch against its base, the changes of the agent's last turn and chosen commits. The All files tab shows any file in the worktree, and the PR tab mirrors the open pull request or merge request from GitHub, GitLab or Azure DevOps read-only. `fff` searches files and code, find in file steps through matches, and Markdown flips between source and rendered view with `m`. The plugin installs with `herdr plugin install persiyanov/herdr-reviewr` and opens itself when herdr creates a workspace for a worktree. The binary also runs without herdr: `herdr-reviewr ~/some/repo`.
Who it is for. For developers who run Claude Code, Codex, OpenCode or Pi inside herdr and want to read and comment on their edits without leaving the terminal.
Good fit when
- The agent finished a task and you want to read its edits line by line instead of trusting the chat summary
- Notes on several places in the code need to go to the agent in one message
- You want to see only what changed in the agent's last turn, apart from the other edits on the branch
- You want a mirror view of the pull request and its checks next to the diff
- You want to view a whole worktree file next to the diff, including Markdown in rendered form
Not a fit when
- The agent does not run inside herdr: the send button and the last-turn scope are unavailable without it
- You need comments that survive between sessions: they live in memory and vanish when the pane closes
- The terminal lacks 24-bit color: there is no 256 or 8 color fallback, so colors come out wrong
Example request
Open herdr-reviewr next to the agent and show me the branch diff: I will comment on a couple of spots and send the notes backLimitations
- Needs herdr 0.9.3 or newer, git on `PATH` and a terminal with 24-bit color and Unicode box-drawing. Runs on macOS, Linux and Windows.
- Sending needs an agent in the workspace: with one agent comments go straight away, with several a picker opens, and if the agent waits at a permission prompt the send is refused and the comments stay.
- Comments live only in the memory of one session. Send and copy deliver the whole set at once, and on failure everything stays in place. Line numbers are not rebased, a stale comment is located by its diff snippet and flagged.
- The PR tab needs an already authenticated `gh`, `glab` or `az` with the `azure-devops` extension and a recognized `upstream` or `origin`. Only the open pull request is mirrored, and each comment surface caps at the newest 100 rows.
- The theme is not picked from the terminal automatically, you match it by hand from 20 palettes. Red and green for removals and additions still have no secondary cue for colorblind users.
How to disable. Remove the plugin with `herdr plugin uninstall persiyanov.reviewr`. To stop the pane from opening itself, set `auto_open = false` in `~/.config/herdr/plugins/config/persiyanov.reviewr/config.toml`. The standalone binary is removed like any file.
FAQ
What is the last-turn scope?
It shows everything that changed in the worktree since the most recent agent turn started. If the agent's first write lands just as the turn begins and cannot be told apart from the snapshot, the scope shows nothing and says why instead of part of the edits.
Does the plugin change my code or send anything on its own?
No, it never edits the worktree and sends nothing without your command. The PR tab reads forge data and posts nothing there.
How do I view the diff of one or several commits?
The commits scope is chosen with `g` and the commit set with `G`. This lets you read what the agent committed step by step, without its unsaved edits.
How do I change the editor and the theme?
`e` opens the file in the editor from `$EDITOR`, `$VISUAL` or git's `core.editor`, and the `editor` config key takes a command with `{file}` and `{line}`. The theme is set with the `theme` key or the `--theme` flag, and the default is `catppuccin`.
How does code search work in the pane?
`/` searches file names fuzzily and code contents across the worktree, powered by `fff`. `Ctrl+F` searches inside the open file and steps between matches.
What if the forge remote is not recognized?
The PR tab tells you what to fix: you need an authenticated `gh`, `glab` or `az` and a readable `upstream` or `origin`. The other tabs keep working, and other forges are not supported.
Discussion
No questions or reviews yet.
Related
CLI toolsA code-review CLI and plugin for agents: reads a git diff and writes line-level comments with context
A CLI that opens a local git diff in the browser like GitHub's Files changed tab; comments copy out as prompts for an agent
A terminal diff viewer: all files in one stream, and an agent with the hunk-review skill walks through the changes and leaves line comments
Crit opens a coding agent's plans, diffs and running apps in a browser: click a line, leave a comment and the agent receives it
A Claude Code plugin: Claude does the task, then a stop hook starts an independent Codex review and Claude fixes the findings in the same session
A terminal multiplexer built for coding agents: keeps Claude Code, Codex and Cursor sessions running after you disconnect and combines several machines in one w
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| herdr-reviewr (this entry) | no | 928 | |
| herdr | no | 45,395 | the terminal multiplexer for coding agents itself, and the plugin installs into it |
| open-code-review | no | 48,062 | the agent does the review: it reads the git diff and writes line notes, while here a human reads and comments the diff |
README in short
The repository holds a Rust project with prebuilt releases, release documentation and notes on the herdr API in `docs`, a changelog, security and contribution rules, color themes, demo scripts and a recording of the tool at work. The main page covers installation, a five-step quick start, key tables, diff scopes, configuration keys, a limitations section and a roadmap.