ccs
Switch between Claude accounts, Gemini, Copilot, OpenRouter (300+ models) via CLIProxyAPI OAuth proxy. Visual dashboard, remote proxy support, WebSearch fallback. Zero-config to production-ready.
Runs with mockssource: GitHubhomepageTypeScriptMITcommit f45fa923f231
TypeScript, MIT licensed. The project labels itself: ai gateway, anthropic api, claude, claude code, cli tool, cliproxyapi, developer productivity and gemini.
ccs runs, with stand-ins for the services it depends on. An Argusic agent installed it in 11 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The project builds, the ccs CLI launches without config errors, and the tool-sanitization proxy plus related integration tests (75 tests across 5 files) pass 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 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.
- 3 tool-sanitization proxy tests failed: forwardJsonBuffered passed transfer-encoding alongside content-length headers5 minutes
- config.yaml had version: '2.0' as a string; isUnifiedConfig() requires a number2 minutes
- bun not found in PATH1 minute
- Install time
- 11 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- bun test on proxy, config, upstream-timeout, messages-endpoint, request-routing files: 75 pass, 0 fail; node dist/ccs.js --version returns v8.10.0 with no errors
- Model tokens used
- 142,538
- Exact commit tested
- f45fa923f231
- 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.
1. **Install & build** — Bun was missing (first error); installed it. Then `bun install` and `bun r… 2. **Config error** — The postinstall fallback created `~/.ccs/config.yaml` with `version: '2.0'` a… 3. **3 test failures fixed** — `tool-sanitization-proxy-integration.test.ts` had 3 tests consistent… 4. **Verification** — `node dist/ccs.js --version` prints v8.10.0 with no errors; `ccs doctor` runs… tokens used 142,538 The task is complete. Here's the summary: **What happened:** 1. **Install & build** — Bun was missing (first error); installed it. Then `bun install` and `bun r… 2. **Config error** — The postinstall fallback created `~/.ccs/config.yaml` with `version: '2.0'` a… 3. **3 test failures fixed** — `tool-sanitization-proxy-integration.test.ts` had 3 tests consistent… 4. **Verification** — `node dist/ccs.js --version` prints v8.10.0 with no errors; `ccs doctor` runs…
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
- Installed in 11 minutes, faster than the median of the 6 comparable projects Argusic has measured.
- Recovered from all 3 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.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 7 ai-gateway projects Argusic has installed and timed, ccs was the 3rd fastest to reach a running state, and 5 of 7 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.22 |
Topics (from GitHub)
ai-gatewayanthropic-apiclaudeclaude-codecli-toolcliproxyapideveloper-productivitygeminigithub-copilotmulti-accountnodejsoauthopenrouterprofile-switchingreact-dashboardtypescriptwebsearch
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ccs)Questions
- Does ccs run?
- ccs runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 11 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test ccs?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f45fa923f231. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test ccs?
- The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ccs take to install?
- 11 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 ccs need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ccs?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ccs compare with the alternatives?
- Of the 7 ai-gateway projects Argusic has installed and timed, ccs was the 3rd fastest to reach a running state, and 5 of 7 reached one at all.
- Where is the evidence for ccs?
- 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.