quotio
Stop juggling AI accounts. Quotio is a beautiful native macOS menu bar app that unifies your Claude, Gemini, OpenAI, Qwen, and Antigravity subscriptions, with real-time quota tracking and smart auto-failover for AI coding tools like Claude Code, OpenCode, and Droid.
Runs with mockssource: GitHubhomepageRustMITcommit dfa5beeb59cd
Rust, MIT licensed. The project labels itself: ai tools, developer tools, proxy and quota monitor.
quotio runs, with stand-ins for the services it depends on. An Argusic agent installed it in 19 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
quotio CLI 1.0.0-beta.4 installs and runs on Linux, its full Rust test suite passes 634/634, and `serve --no-saved-accounts` returns HTTP 200 schema-2 JSON on /v2/snapshot; macOS/iOS apps were not runnable in this Linux container.
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 92 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.
- 19 suite tests failed: hard-coded /usr/bin/sqlite3 missing (NotFound)15 minutes
- serve default returned 503 credential_storage_unavailable on Linux2 minutes
- npm global install EACCES /usr/local/lib/node_modules1 minute
- quotio serve --port rejected (Invalid arguments)1 minute
- Install time
- 19 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- cargo test --manifest-path apps/cli/Cargo.toml --locked --all-features exited 0 (634 passed, 0 failed); curl -s -o /dev/null -w %{http_code} http://127.0.0.1:6767/v2/snapshot returned 200
- Model tokens used
- 517,111
- Exact commit tested
- dfa5beeb59cd
- 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.
- Default `serve` returned `HTTP 503 credential_storage_unavailable` (expects Keychain-style vault;…
- Fix: `--no-saved-accounts` (documented bypass) → `HTTP 200`. 2 min.
**Final verification**
- 2 clean full runs, each exit 0: `538 passed, 0 failed, 1 ignored` (unit) + integration suites `2 …
- Source build succeeded: `cargo build --manifest-path apps/cli/Cargo.toml --locked --all-features`…
- `curl -s -o /tmp/qserved/snap4.json -w "%{http_code}" http://127.0.0.1:6767/v2/snapshot` → `200`,…
MacOS/iOS targets were not runnable (no macOS/Xcode in this container; checked `swift`, `xcodebuild…
**Errors** (msg, fix, minutes)
- `npm global install EACCES /usr/local/lib/node_modules` → `npm config set prefix "$HOME/.npm-glob…
- `19 tests failed: /usr/bin/sqlite3 NotFound (fixtures use hard-coded path)` → `added PATH-resolvi…
- `quotio serve --port rejected (Invalid arguments)` → `documented flag is --listen 127.0.0.1:6767`…
- `serve returned 503 credential_storage_unavailable (Linux no vault)` → `--no-saved-accounts bypas…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 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 19 minutes to install, slower than the median of the 15 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 16 ai-tools projects Argusic has installed and timed, quotio was the 15th fastest to reach a running state, and 11 of 16 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 | 1/3 | Runs with mocks | 92.00 | 0.13 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/quotio)Questions
- Does quotio run?
- quotio runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 19 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test quotio?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dfa5beeb59cd. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test quotio?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does quotio take to install?
- 19 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 quotio need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing quotio?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does quotio compare with the alternatives?
- Of the 16 ai-tools projects Argusic has installed and timed, quotio was the 15th fastest to reach a running state, and 11 of 16 reached one at all.
- Where is the evidence for quotio?
- 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.