router
Model router for agentic systems. Routes every prompt to the right model in <50ms. Cut costs 40-70% with just an endpoint change.
Could not verifysource: GitHubhomepageGoApache-2.0commit 6f4674498ac2
Go, Apache-2.0 licensed. The project labels itself: agentic coding, ai gateway, anthropic, claude code, codex, model router and openai compatible.
Argusic could not get router running. An Argusic agent installed it in 34 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Build and test suite pass (0 failures). Router binary compiles with ORT+CGO but requires ONNX Runtime library, Jina embedder ONNX model files, and a GCP Pub/Sub emulator to serve HTTP; gateway binary and all non-CGO code compile and test cleanly.
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 50 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.
- Test failure: TestNewTransport_ConfiguresHTTP2Keepalives — Go 1.27+ changed http2.ConfigureTransports to use Protocols/RegisterProtocol instead of TLSNextProto10 minutes
- Router needs CGO + ORT tag + ONNX Runtime library + libtokenizers for cluster scorer embedder5 minutes
- Router needs GCP Pub/Sub emulator (gRPC) for cache invalidation — Java or Docker required5 minutes
- Router needs Jina v2 model files from HuggingFace for embedder3 minutes
- Go 1.25+ not installed2 minutes
- Install time
- 34 minutes
- Cold machine to finish
- 39 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- go test ./... passed with 0 failures across all packages; go build ./... passed for all packages and binaries; go test -count=1 ./internal/providers/httputil verified the Go 1.27 compatibility fix
- Model tokens used
- 666,522
- Exact commit tested
- 6f4674498ac2
- 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.
Let me clean up and do a final summary: 2026-09-24T08:00:11.705925Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce… exec /bin/sh -lc '# Clean up background processes safely /tmp/bin/pg_ctl -D /tmp/pgdata stop 2>/dev/null || true echo "done"' in /work/repo succeeded in 0ms: waiting for server to shut down.... done server stopped done tokens used 666,522
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
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
- Took 34 minutes to install, slower than the median of the 9 comparable projects Argusic has measured.
Of the 10 agentic-coding projects Argusic has installed and timed, router was the 9th fastest to reach a running state, and 8 of 10 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 | 2/3 | Did not run | 50.00 | 0.44 | |
| Argusic Runner | 1/3 | Did not run | 50.00 | 0.03 |
Topics (from GitHub)
agentic-codingai-gatewayanthropicclaude-codecodexmodel-routeropenai-compatible
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/router)Questions
- Does router run?
- Argusic could not verify that router runs. Argusic installed and launched it on a clean machine in 34 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test router?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6f4674498ac2. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test router?
- The run that produced this verdict cost $0.44: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does router take to install?
- 34 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 router need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing router?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does router compare with the alternatives?
- Of the 10 agentic-coding projects Argusic has installed and timed, router was the 9th fastest to reach a running state, and 8 of 10 reached one at all.
- Where is the evidence for router?
- 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.