herdr-reviewr
Review your agent's diff in a terminal pane and send comments back to Claude Code, Codex, OpenCode or Pi. A herdr plugin.
Runssource: GitHubRustMITcommit c9a187ff2e70
Rust, MIT licensed. The project labels itself: agentic coding, ai agents, claude code, cli, code review, code review tool, codex and coding agents.
herdr-reviewr runs. An Argusic agent installed it in 14.9 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The Rust project builds, all 1009 tests pass, the release binary launches as a TUI under a PTY and quits cleanly, and the plugin config resolution works.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- 15 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- `just test` exited 0: 1009 tests passed (378+334+61+29+45+161+1), 0 failed, 1 ignored. Release binary launched under PTY, stayed alive 3s rendering TUI, quit cleanly with exit 0 on 'q'. `--resolve-plugin-config` returned full JSON config. `just fmt-check` and `just lint` both passed.
- Model tokens used
- 54,786
- Exact commit tested
- c9a187ff2e70
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
ok. 378 passed ok. 0 passed ok. 334 passed ok. 61 passed ok. 29 passed ok. 45 passed ok. 0 passed ok. 161 passed ok. 1 passed ok. 0 passed tokens used 54,786
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 14.9 minutes to install, slower than the median of the 29 comparable projects Argusic has measured.
Of the 30 agentic-coding projects Argusic has installed and timed, herdr-reviewr was the 24th fastest to reach a running state, and 23 of 30 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- Following its own README: the documented path worked with nothing to fix.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agentic-codingai-agentsclaude-codeclicode-reviewcode-review-toolcodexcoding-agentsdeveloper-toolsdiffgitherdrherdr-pluginopencoderatatuirustterminaltui
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/herdr-reviewr)Questions
- Does herdr-reviewr run?
- Yes. herdr-reviewr runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test herdr-reviewr?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c9a187ff2e70. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test herdr-reviewr?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does herdr-reviewr take to install?
- 14.9 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does herdr-reviewr need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing herdr-reviewr?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does herdr-reviewr compare with the alternatives?
- Of the 30 agentic-coding projects Argusic has installed and timed, herdr-reviewr was the 24th fastest to reach a running state, and 23 of 30 reached one at all.
- Where is the evidence for herdr-reviewr?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.