llmio
Unified LLM gateway with weighted load balancing, observability & cost tracking. 统一的 LLM 网关,提供权重负载均衡、可观测性与费用追踪。
Runssource: GitHubGoMITcommit 3919f3385eb3
Go, MIT licensed. The project labels itself: ai, ai gateway, claude, claude ai, claude code, codex, deepseek and doubao.
llmio runs. An Argusic agent installed it in 10.2 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The LLMIO Go server builds, the webui builds via pnpm, all 31 Go unit tests pass, and the server starts on :7070 serving the webui and responding to all API endpoints.
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 100 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.
- pnpm ERR_PNPM_IGNORED_BUILDS for @swc/core, esbuild, @tailwindcss/oxide4 minutes
- Go binary not found in PATH1.5 minutes
- npm install failed due to peer dependency conflicts1 minute
- pnpm not found0.5 minutes
- Go build failed: pattern webui/dist: no matching files found0.3 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- curl -s -H "Authorization: Bearer test123456" http://localhost:7070/openai/v1/models returned 200 with '{"object":"list","data":[]}'; curl -s -o /dev/null -w '%{http_code}' http://localhost:7070/ returned 200; go test -count=1 ./... passed 31 tests across 4 packages (balancers, middleware, models, service)
- Model tokens used
- 581,020
- Exact commit tested
- 3919f3385eb3
- 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 , the attempt that decided the verdict above. 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.
{"code":200,"message":"success","data":"dev"}
[GIN] 2026/10/24 - 19:32:03 | 200 | 2.764449ms | 127.0.0.1 | GET "/assets/index-D3xA4…
Assets: 200
[GIN] 2026/10/24 - 19:32:03 | 401 | 29.544µs | 127.0.0.1 | GET "/api/providers"
Unauth: 401
All endpoints verified. Let me clean up and record:
2026-10-24T19:32:09.615099Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce…
exec
/bin/sh -lc 'cd /work/repo && export PATH="/home/runner/.go/go/bin:/home/runner/.npm-global/bin:$PA…
exited 143 in 0ms:
tokens used
581,020Replay 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.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 10.2 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 237 ai projects Argusic has installed and timed, llmio was the 176th fastest to reach a running state, and 168 of 237 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.
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
Topics (from GitHub)
aiai-gatewayclaudeclaude-aiclaude-codecodexdeepseekdoubaogeminigemini-cligogolangkiminewapiopenaiopenclawqwentransformer
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/llmio)Questions
- Does llmio run?
- Yes. llmio runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test llmio?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3919f3385eb3. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test llmio?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does llmio take to install?
- 10.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 llmio need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing llmio?
- 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 llmio compare with the alternatives?
- Of the 237 ai projects Argusic has installed and timed, llmio was the 176th fastest to reach a running state, and 168 of 237 reached one at all.
- Where is the evidence for llmio?
- 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.