cc-switch
A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io
Could not verifysource: GitHubhomepageRustMITcommit db41d7018795
Rust, MIT licensed. The project labels itself: ai tools, claude code, codex, desktop app, grok, grokbuild, hermes and hermes agent.
Argusic could not get cc-switch running. An Argusic agent installed it in 41 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Frontend build, typecheck, and all 1075 unit tests pass; Rust/Tauri native binary cannot compile without system -dev packages
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 65 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.
- Rust/Tauri backend cannot compile: missing system dev packages (webkit2gtk-4.1-dev, libgtk-3-dev, etc.) - no root access to apt-get install25 minutes
- Install time
- 41 minutes
- Cold machine to finish
- 42 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- Model tokens used
- 315,919
- Exact commit tested
- db41d7018795
- 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.
- 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
- 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.
coverage: {
reporter: ["text", "lcov"],
},
},
});
Good - the `testTimeout: 15000` fix is appropriate for the environment. Now let me compute the fina…
Install time: I started around 16:14, it's now 16:55 (roughly). The install (pnpm install + Rust in…
2026-09-06T16:52:23.488453Z ERROR codex_core::session: failed to record rollout items: thread 01a07…
tokens used
315,919
Good - the `testTimeout: 15000` fix is appropriate for the environment. Now let me compute the fina…
Install time: I started around 16:14, it's now 16:55 (roughly). The install (pnpm install + Rust in…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 1 error without a human stepping in, which says the failures are documented well enough to solve.
- 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.
- Took 41 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
Of the 4 ai-tools projects Argusic has installed and timed, cc-switch was the 4th fastest to reach a running state, and 3 of 4 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 | 2/3 | Did not run | 50.00 | 0.25 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.17 |
Topics (from GitHub)
ai-toolsclaude-codecodexdesktop-appgrokgrokbuildhermeshermes-agentmcpopen-sourceopenclawopenclaw-uiopencodepiprovider-managementrustskillsskills-managementtauriwsl-support
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cc-switch)Questions
- Does cc-switch run?
- Argusic could not verify that cc-switch runs. Argusic installed and launched it on a clean machine in 41 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test cc-switch?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit db41d7018795. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test cc-switch?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cc-switch take to install?
- 41 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 cc-switch need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cc-switch?
- 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 cc-switch compare with the alternatives?
- Of the 4 ai-tools projects Argusic has installed and timed, cc-switch was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for cc-switch?
- 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.