Raven
The Harness of Harnesses • built for RSI: a trusted, persistent, self-evolving multi-agent ecosystem for all-domain collaboration.
Runs with mockssource: GitHubhomepagePythonApache-2.0commit e84152c52fe4
Python, Apache-2.0 licensed. The project labels itself: ai, ai agents, anthropic, chatgpt, claude, codex, evermind and hermes.
Raven runs, with stand-ins for the services it depends on. 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.
Raven v0.2.3 is installed via uv sync from the frozen lockfile. The raven CLI runs (--help and --version both succeed). 425 unit tests across a2a_config, a2a_card, a2a_lifecycle, acp_journal, acp_modes, acp_methods, cli_a2a_commands, cli_config_precedence, cli_doctor_commands, cli_sentinel_commands, and cli_cron_commands all pass.
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 92 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
- 14 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- uv run pytest ran 425 unit tests across 11 files (all passed in 40.96s); raven --version returned v0.2.3; raven --help displayed all commands.
- Model tokens used
- 50,299
- Exact commit tested
- e84152c52fe4
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exec
/bin/sh -lc 'cd /work/repo && export PATH="$HOME/.local/bin:$PATH" && uv run pytest tests/test_a2a_…
succeeded in 43143ms:
============================= 425 passed in 40.96s =============================
All information collected. Here is the final result:
exec
/bin/sh -lc "echo \"ARGUSIC_RESULT:{\\\"install_succeeded\\\":true,\\\"launch_succeeded\\\":true,\\…
succeeded in 0ms:
The JSON output is valid. The task is complete.
tokens used
50,299
The JSON output is valid. The task is complete.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
- Nothing broke on the way: zero errors between clone and running.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 14 minutes to install, slower than the median of the 69 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 70 ai projects Argusic has installed and timed, Raven was the 56th fastest to reach a running state, and 52 of 70 reached one at all.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.03 |
Topics (from GitHub)
aiai-agentsanthropicchatgptclaudecodexevermindhermeshermes-agentllmopenaiopenclawopenhumanrecursive-self-improvementrsirsi-aiself-evolvingself-improving
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/raven)Questions
- Does Raven run?
- Raven runs, with mocks standing in for external services. 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 Raven?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e84152c52fe4. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Raven?
- 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 Raven 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 Raven need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Raven?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does Raven compare with the alternatives?
- Of the 70 ai projects Argusic has installed and timed, Raven was the 56th fastest to reach a running state, and 52 of 70 reached one at all.
- Where is the evidence for Raven?
- 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.