crit
Your feedback loop with the agent
Runssource: GitHubhomepageGoMITcommit 2f9a883d138c
Go, MIT licensed. The project labels itself: agentic coding, ai agents, ai tools, cli, code review, developer tools, llm and markdown.
crit runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The crit binary builds, all Go unit tests pass (25 packages), all frontend JS tests pass (85 tests), formatting and linting are clean, and the server starts and serves HTTP on demand, including headless comment creation.
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 96.7 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
- 2 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- go test -count=1 ./... passed (25 packages, 0 failures), npm run test:frontend passed (85 tests, 0 failures), ./crit --version returned 'crit dev', curl http://localhost:3001/ returned 200, curl http://localhost:3001/api/health returned ok, ./crit comment wrote verified JSON to review file
- Model tokens used
- 83,310
- Exact commit tested
- 2f9a883d138c
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
5. `npm run copy-deps` was not needed (vendored assets already existed in `web/`) **Verification steps:** - `go build -o crit ./cmd/crit` — built a 26MB single binary with no errors - `./crit --version` — printed `crit dev` — binary runs and responds - `./crit --help` — printed full help text with all subcommands - `go test -count=1 ./...` — 25 Go packages, all passed, 0 failures - `gofmt -l .` — 0 files unformatted - `golangci-lint run ./...` — 0 issues - `npm run test:frontend` — 5 test files, all passed (30+5+42+4+4 = 85 tests, 0 failures) - `curl http://localhost:3001/` returned `200` and `curl http://localhost:3001/api/health` returned… - `./crit comment test/shell/notification-plan.md:10 "Test comment"` — wrote comment to review file… - `./crit stop` — daemon shutdown correctly
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.
- Installed in 2 minutes.
- 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.
Of the 9 agentic-coding projects Argusic has installed and timed, crit was the 4th fastest to reach a running state, and 8 of 9 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.
- A quick evaluation: it was running 2 minutes after the clone.
- 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-agentsai-toolsclicode-reviewdeveloper-toolsllmmarkdown
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/crit)Questions
- Does crit run?
- Yes. crit runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test crit?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2f9a883d138c. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test crit?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does crit take to install?
- 2 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 crit need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing crit?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does crit compare with the alternatives?
- Of the 9 agentic-coding projects Argusic has installed and timed, crit was the 4th fastest to reach a running state, and 8 of 9 reached one at all.
- Where is the evidence for crit?
- 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.