cline-pass-switcher
Cline Pass 上游控制台, 枚举/校验/钉住订阅模型背后的上游渠道 · 账号池轮询 · OpenAI 兼容代理(零依赖 Node)
Runs with mockssource: GitHubJavaScriptMITcommit 02538a3137a0
JavaScript, MIT licensed. The project labels itself: api gateway, chinese, cline, cline pass, docker, llm proxy, openai compatible and openrouter.
cline-pass-switcher runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.1 minutes and hit 1 error and fixed every one without help 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 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.
- Server crashes after first request when DATA_DIR is repo root without config.json/metadata.json (both in .gitignore)2 minutes
- Install time
- under a minute
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- timeout 15 node server.js with DATA_DIR=/tmp/clean-test, then curl verified GET / (200), /v1/models (200), /api/meta (200), /nonexistent (404); against mock upstream on 3199, POST /v1/chat/completions returned 200 with correct choices/content, POST /api/test returned full trace with ok:true and pipeline:'direct', POST /api/accounts/test returned ok:true in 42ms, POST /api/probe returned ok:True, GET /api/history showed 5 recorded entries, auth enforcement via proxyKey works
- Model tokens used
- 61,425
- Exact commit tested
- 02538a3137a0
- 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.
**Mock-based verification**: I stood up a mock upstream server on `127.0.0.1:3199` and pointed the … - `GET /` — served the control panel HTML - `GET /v1/models` — listed subscription models - `POST /v1/chat/completions` — proxied to mock upstream, returned a valid chat completion with cor… - `POST /api/test` — full upstream trace with status, timing, and provider info - `POST /api/probe` — upstream probe with provider detection - `POST /api/accounts/test` — key validation - `POST /api/security` — proxy key setting (auth required after setting) - `POST /api/config` — per-model config persistence - `GET /api/history` — 5 history entries recorded - All routes: 200; nonexistent routes: 404; auth enforcement works **final_state**: The server starts with `node server.js`, listens on the configured port, serves th…
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 0.1 minutes, faster than the median of the 31 comparable projects Argusic has measured.
- Recovered from all 1 error 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 32 api-gateway projects Argusic has installed and timed, cline-pass-switcher was the 4th fastest to reach a running state, and 22 of 32 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.11 |
Topics (from GitHub)
api-gatewaychineseclinecline-passdockerllm-proxyopenai-compatibleopenrouterupstream-switchervercel-ai-gateway
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cline-pass-switcher)Questions
- Does cline-pass-switcher run?
- cline-pass-switcher runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test cline-pass-switcher?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 02538a3137a0. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test cline-pass-switcher?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cline-pass-switcher take to install?
- 0.1 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 cline-pass-switcher need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cline-pass-switcher?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does cline-pass-switcher compare with the alternatives?
- Of the 32 api-gateway projects Argusic has installed and timed, cline-pass-switcher was the 4th fastest to reach a running state, and 22 of 32 reached one at all.
- Where is the evidence for cline-pass-switcher?
- 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.