chief

Build big projects with Claude. Chief breaks your work into tasks and runs Claude Code in a loop until they're done.

Runssource: GitHubhomepageGoMITcommit 3cff99fa2369

Go, MIT licensed. The project labels itself: ai, automation, claude, claude code, cli, developer tools, go and ralph loop.

chief runs. An Argusic agent installed it in 14 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Chief binary builds and runs, all 10 test packages pass, CLI responds to --version, --help, and list commands.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.20 (measured)
recorded runs
1
last tested
stars
474
forks
50
open issues
20
watchers
2
size
6 MB
created
last push

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
14 minutes
Cold machine to finish
15 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
go test ./... exited 0 (10 packages, 1297 test cases); ./bin/chief --version returned 'chief version test'; ./bin/chief --help printed usage; ./bin/chief list returned 'No PRDs found'
Model tokens used
139,258
Exact commit tested
3cff99fa2369
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.

139,258
All good. Here's the final report:
The project is a Go (golang) binary called **Chief** – an autonomous agent loop for implementing PR…
**Installation steps:**
- Downloaded Go 1.24.13 prebuilt binary from `go.dev` to `/home/runner/.go/go/bin/go`
- Built the project: `go build -ldflags "-X main.Version=test" -o bin/chief ./cmd/chief`
- Ran the test suite: all 10 packages passed (1297 test cases across markdown parsing, watcher, age…
**Verification:**
- `./bin/chief --version` → `chief version test`
- `./bin/chief --help` → prints full usage, 27 lines, all commands online
- `./bin/chief list` → `No PRDs found. Run 'chief new' to create one.` (expected, no PRD yet)
- `go test ./...` → all packages `ok`

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.

What did not, or is not known

  • Took 14 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 237 ai projects Argusic has installed and timed, chief was the 192nd fastest to reach a running state, and 168 of 237 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.20

Topics (from GitHub)

aiautomationclaudeclaude-codeclideveloper-toolsgoralph-looptui

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/chief.svg)](https://argusic.com/subject/chief)

Questions

Does chief run?
Yes. chief runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test chief?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3cff99fa2369. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test chief?
The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does chief take to install?
14 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 chief need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing chief?
Nothing did, in the recorded run: zero errors between clone and running.
How does chief compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, chief was the 192nd fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for chief?
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.

Discussion