Yes. hive runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 2 errors on the way, and recorded the session.

How did Argusic test hive?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6193aea7eb06. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test hive?

The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does hive take to install?

0.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 hive need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing hive?

2 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for hive?

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.

hive

Multi-Agent Harness for Production AI

Runssource: GitHubPythonApache-2.0commit 6193aea7eb06

Python, Apache-2.0 licensed. The project labels itself: agent, agent framework, agent skills, anthropic, automation, autonomous agents, claude and harness.

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

All Python dependencies installed and both framework and tools packages build successfully. Core test suite (2500 tests) passes cleanly. Tools test suite (6840 of 7261 tests) passes with one pre-existing endpoint mismatch failure. The hive CLI launches and displays help text.
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 90 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 90 / 100
cost of the verifying run: $0.07 (measured)
recorded runs: 1
last tested: 2026-09-27
stars: 11,075
forks: 5,658
open issues: 1,357
watchers: 239
size: 25 MB
created: 2026-01-12
last push: 2026-09-14

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-27. 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.

Time lost to each failure while testing hive, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Playwright browser binaries missing0.2 minutes
test_live_health_checks.py::TestLiveIntegrationWiring::test_wiring_valid[lusha_api_key] — endpoint mismatch between spec and checker URL

Install time: under a minute
Cold machine to finish: 20 minutes
Errors hit and fixed: 2 hit, 1 fixed with no human help
How the result was proved: uv run python -m pytest core/tests/ (2500 passed); uv run python -m pytest tools/tests/ (6840 passed, 420 skipped, 1 failed); uv run hive --help printed usage
Model tokens used: 322,486
Exact commit tested: 6193aea7eb06
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.

- **Tools tests** — 6840 passed, 420 skipped, **1 pre-existing failure** (a wiring mismatch in `tes…
- **`hive` CLI** — prints help and subcommand help correctly.
- **Chart tests** — initially 3 failures due to Playwright browsers not being installed; fixed by r…
tokens used
322,486
Now I have everything. Let me compile the final result.
**Summary of what happened:**
- **`uv sync`** — installed all 129 packages successfully. Both `framework` and `tools` built.
- **Core tests** — 2500 passed, 15 skipped, 4 deselected. No failures.
- **Tools tests** — 6840 passed, 420 skipped, **1 pre-existing failure** (a wiring mismatch in `tes…
- **`hive` CLI** — prints help and subcommand help correctly.
- **Chart tests** — initially 3 failures due to Playwright browsers not being installed; fixed by r…

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 0.3 minutes, faster than the median of the 45 comparable projects Argusic has measured.
Ran without a GPU, so it does not need one to start.
Licensed Apache-2.0, as reported by its host.

What did not, or is not known

Hit 2 errors 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 46 agent projects Argusic has installed and timed, hive was the 3rd fastest to reach a running state, and 33 of 46 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 0.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

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	90.00	0.07	2026-09-27 10:36 UTC

Topics (from GitHub)

agent agent-framework agent-skills anthropic automation autonomous-agents claude harness harness-engineering human-in-the-loop openai python self-hosted self-improving

Embed the badge

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

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

Questions

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