codex-router
External-model router for Codex with guided Kimi OAuth/API, DeepSeek, safe migration, and rollback.
Could not verifysource: GitHubJavaScriptMITcommit 0a70b48c0ed7
JavaScript, MIT licensed. The project labels itself: codex, deepseek, kimi, litellm and model router.
Argusic could not get codex-router running. An Argusic agent hit no errors on a clean machine with no GPU, and the whole session was recorded.
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 20 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.
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- Exact commit tested
- 0a70b48c0ed7
- 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.
- Install time
- the run did not report one
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Model tokens used
- not recorded for this run
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
... succeeded in 1040ms: runner 1024 0.0 2.3 609932 47432 ? Sl 09:26 0:00 node /usr/local/bin/codex exec --s… runner 1039 0.4 7.7 559476 155336 ? Sl 09:26 0:03 /usr/local/lib/node_modules/@opena… runner 22300 10.1 4.0 1102492 81316 ? Sl 09:37 0:00 /home/runner/.n/bin/node /work/rep… runner 22329 16.3 3.8 1103188 78072 ? Ssl 09:37 0:00 /home/runner/.n/bin/node /work/rep… runner 22349 11.3 3.7 1101184 76576 ? Rl 09:37 0:00 /home/runner/.n/bin/node /work/rep… exec /bin/sh -lc 'kill 22300 22329 22349 2>/dev/null; sleep 1; echo "done"' in /work/repo succeeded in 851ms: done That previous install run left some nodes running. Let me clean up and take a more controlled appro…
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 MIT, 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.
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 | 20.00 | 0.07 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.06 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/codex-router)Questions
- Does codex-router run?
- Argusic could not verify that codex-router runs. Argusic installed and launched it on a clean machine, hitting 0 errors on the way, and recorded the session.
- How did Argusic test codex-router?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0a70b48c0ed7. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test codex-router?
- 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.
- Does codex-router need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing codex-router?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for codex-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.