hunk
Review-first terminal diff viewer for agentic coders
Runssource: GitHubhomepageTypeScriptMITcommit aa23ba29ae23
TypeScript, MIT licensed. The project labels itself: agents, cli, code review, diff, git, jj, jujutsu and sapling.
hunk runs. An Argusic agent installed it in 3 minutes and hit 1 error on a clean machine with no GPU, and the whole session was recorded.
Hunk 0.23.0 builds from source with Bun 1.4.2, passes typecheck, runs its CLI (help, version, log, diff commands), and passes 2372/2383 default tests. 1 pre-existing daemon timing test fails, website tests require optional playwright dependencies, and the changeset versioning test requires Node 22+.
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 80 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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- canonical changelog versioning test fails - @changesets/[email protected] requires Node.js 22+ due to ESM/CJS human-id incompatibility10 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 37 minutes
- Errors hit and fixed
- 1 hit, 0 fixed with no human help
- How the result was proved
- bun run test: 2372 pass, 10 skip, 1 fail (pre-existing daemon timing test). Typecheck passed. bun run packages/hunk/src/main.tsx --help and --version 0.23.0 both work.
- Model tokens used
- 276,787
- Exact commit tested
- aa23ba29ae23
- 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.
- `bun run typecheck` (tsc --noEmit) — passed with zero errors - `bun run packages/hunk/src/main.tsx --help` — works and prints the full help - `bun run packages/hunk/src/main.tsx --version` → `0.23.0` - `bun run test` — ran the full default test suite across 2 shards **Pre-existing failures** (verified by running tests against pristine source): 1. **`canonical changelog versioning`** — Requires Node 22+ for `@changesets/[email protected]` (we have N… 2. **`Hunk session daemon client > authenticates after a successor becomes healthy`** — A timing-se… 3. **Website tests** — Missing `@playwright/test` and `@axe-core/playwright` modules. These aren't … **Fixed fixes** (2 applied): 1. **log.test.ts** — The test expected Git date format `Z` for UTC timestamp, but Git 2.43 on Ubunt… 2. **source.ts (hunk-jj)** — The spawn-error diagnostic for Jujutsu source reads omitted the `repoR… Both fixes verified passing.
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 3 minutes, faster than the median of the 21 comparable projects Argusic has measured.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Hit 1 error during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 22 agents projects Argusic has installed and timed, hunk was the 5th fastest to reach a running state, and 13 of 22 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 3 minutes after the clone.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hunk)Questions
- Does hunk run?
- Yes. hunk runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test hunk?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit aa23ba29ae23. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test hunk?
- The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hunk take to install?
- 3 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 hunk need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hunk?
- 1 thing broke in the recorded run. Each one, and the time it cost, is listed on this page.
- How does hunk compare with the alternatives?
- Of the 22 agents projects Argusic has installed and timed, hunk was the 5th fastest to reach a running state, and 13 of 22 reached one at all.
- Where is the evidence for hunk?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.