cersei

The Rust SDK for building coding agents. Tools, streaming, graph, sub-agent orchestration, MCP, as composable functions

Runssource: GitHubhomepageRustMITcommit 708c5055845b

Rust, MIT licensed. The project labels itself: agent, antrophic, claude code, codex, coding agent, openai, opencode and rust.

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

The 19-crate Rust workspace builds cleanly, all 612 tests pass, and the abstract-cli binary responds to --help and --version 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.03 (measured)
recorded runs
2
last tested
stars
466
forks
77
open issues
10
watchers
10
size
94 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
7 minutes
Cold machine to finish
6 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
cargo test --workspace: 612 passed, 0 failed; cargo run --bin abstract -- --version printed 'abstract 0.2.6'; cargo run --bin abstract -- --help printed full usage with 16 subcommands/options
Model tokens used
94,297
Exact commit tested
708c5055845b
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.

**Errors**: None encountered. No fixes were needed.
```
```
tokens used
94,297
All tasks completed successfully. Here's my report:
**Install**: Rust toolchain installed via rustup (stable 1.99.1). Workspace built in one shot — `ca…
**Tests**: `cargo test --workspace` — 612 passed, 0 failed across all crates (unit + integration + …
**Binary**: `abstract --help` and `abstract --version` both produced correct output (abstract 0.2.6…
**Errors**: None encountered. No fixes were needed.
```
```

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 7 minutes to install, slower than the median of the 140 comparable projects Argusic has measured.

Of the 141 agent projects Argusic has installed and timed, cersei was the 76th fastest to reach a running state, and 94 of 141 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 7 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.03
Argusic Runner1/3Ran out of time0.000.09

Topics (from GitHub)

agentantrophicclaude-codecodexcoding-agentopenaiopencoderust

Embed the badge

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

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

Questions

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

Discussion