magpie
Every agent's model. One place. Codex on DeepSeek, Claude Code on Kimi, from the menu bar.
Runssource: GitHubhomepageGoMITcommit 22358d5d6eee
Go, MIT licensed. The project labels itself: claude code, codex, deepseek, gemini cli, llm and macos.
magpie runs. An Argusic agent installed it in 8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Magpie CLI binary compiled and runs as a gateway server. All 30 test packages pass on the nogui build. The server answers /v1/models with 200, rejects unknown models with 404, and healthcheck exits 0.
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go compiler (golang) not installed in container3 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- go test -tags nogui ./... exited 0, 30 test packages all ok; curl http://127.0.0.1:3428/v1/models returned HTTP 200 with valid JSON; POST to /v1/chat/completions returned HTTP 404 with expected error; magpie healthcheck exited 0
- Model tokens used
- 61,843
- Exact commit tested
- 22358d5d6eee
- 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.
"msg": "Go compiler (golang) not installed in container",
"fix": "Downloaded Go 1.27.1 from go.dev and extracted to /home/runner/tools/go/go",
"minutes": 3
}
],
"test_depth": "tier1_real",
"verified_how": "go test -tags nogui ./... exited 0, 30 test packages all ok; curl http://127.0.0…
"notes": "GUI build requires GTK4/WebKitGTK (not installed). CLI-only build (nogui) works. Used '…
"final_state": "Magpie CLI binary compiled and runs as a gateway server. All 30 test packages pas…
}
tokens used
61,843Replay 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.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- 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 8 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 claude-code projects Argusic has installed and timed, magpie was the 4th fastest to reach a running state, and 4 of 5 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 8 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/magpie)Questions
- Does magpie run?
- Yes. magpie runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test magpie?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 22358d5d6eee. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test magpie?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does magpie take to install?
- 8 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 magpie need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing magpie?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does magpie compare with the alternatives?
- Of the 5 claude-code projects Argusic has installed and timed, magpie was the 4th fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for magpie?
- 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.