Does harnessrouter run?

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

How did Argusic test harnessrouter?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit fc8da524f408. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test harnessrouter?

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

How long does harnessrouter take to install?

1.2 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 harnessrouter need a GPU?

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

What goes wrong when installing harnessrouter?

Nothing did, in the recorded run: zero errors between clone and running.

Where is the evidence for harnessrouter?

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.

harnessrouter

HarnessRouter Community Edition: the self-hosted, Apache-2.0 edition of the unified interface for agent harnesses. Run Codex, Claude Code, Hermes, PI, DSH, and more through one API, with sessions, streaming, files, cancellation, and failure handling. Implements the Unified Harness Protocol (UHP), an open standard. Your keys, your infrastructure.

Runssource: GitHub homepagePythonApache-2.0commit fc8da524f408

Python, Apache-2.0 licensed. The project labels itself: agent api, agent framework, agent harness, ai agents, ai infrastructure, coding agent, conformance testing and deepseek harness.

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

Gateway and runner servers start and respond to health checks; all three test suites (gateway: 622/17, runner: 490/2, protocol conformance: 85/2) 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 96 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 96 / 100
cost of the verifying run: $0.04 (measured)
recorded runs: 2
last tested: 2026-09-23
stars: 4,278
forks: 471
open issues: 32
watchers: 28
size: 48 MB
created: 2026-08-09
last push: 2026-11-07

Subject data from GitHub, linked at the top of this page, refreshed 2026-11-07. 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: 1 minutes
Cold machine to finish: 6 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: Gateway tests: 622 passed, 17 skipped. Runner tests: 490 passed, 2 skipped. Protocol conformance tests: 85 passed, 2 skipped. Gateway HTTP endpoints: /healthz=200, /readyz=200, /version=200. Runner /healthz=200.
Model tokens used: 89,556
Exact commit tested: fc8da524f408
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run 2026-09-23. The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

sleep 3
echo "runner healthz: $(curl -s -o /dev/null -w '"'%{http_code}' http://127.0.0.1:8081/healthz)\"
tail -5 /tmp/runner.log" in /work/repo
 succeeded in 2865ms:
runner healthz: 200
Now let me clean up and compile the final report.
exec
/bin/sh -lc 'kill $(cat /tmp/gw.pid) $(cat /tmp/runner.pid) 2>/dev/null; echo "cleaned up"' in /wor…
 succeeded in 0ms:
cleaned up
tokens used
89,556

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 1.2 minutes.
Nothing broke on the way: zero errors between clone and running.
Ran without a GPU, so it does not need one to start.
Licensed Apache-2.0, as reported by its host.
Measured 2 times, so the result is not a one-off.

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 1.2 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 by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs	100.00	0.04	2026-09-23 10:21 UTC
Argusic Runner	1/3	Runs with mocks	92.00	0.08	2026-09-23 07:33 UTC

Embed the badge

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

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

Questions

Does harnessrouter run?: Yes. harnessrouter runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test harnessrouter?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit fc8da524f408. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test harnessrouter?: The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does harnessrouter take to install?: 1.2 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 harnessrouter need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing harnessrouter?: Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for harnessrouter?: 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.