cc-switch: one place for every AI tool’s provider
Recommended, and a partner: cc-switch is built by a partner of ours, and this section recommends it outright. It is not a dependency you must install — but if you run several AI command-line tools, it is currently the least painful way to manage them. We recommend it because it solves the configuration problems our customers hit most often, not because of the partnership.
cc-switch is a cross-platform desktop app for developers who use several AI tools at once: one interface for the API provider configuration of 10 tools. Add AllTokens once, then switch with a click.
- Website: ccswitch.io
- Official docs: ccswitch.io/zh/docs
- Source and releases: github.com/farion1231/cc-switch
What it solves
If you use Claude Code and Codex side by side, you have probably hit these:
- Switching providers means editing files every time you move between an official account and a relay provider.
- Configuration is scattered and inconsistent — JSON, TOML, YAML,
.env, in different locations per tool. - No visibility into spend — how many calls, how much money.
- One flaky provider stops everything.
cc-switch puts all of that behind one interface.
Why it is worth installing here
AllTokens SI exposes two API paths — OpenAI-compatible and Anthropic-compatible (see Configure AllTokens) — and different tools speak different protocols. The mistake people make by hand is whether the Base URL should include /v1, which is exactly the part cc-switch keeps straight for you.
Beyond that, the features that matter for teams using our service:
- One-click switching between AllTokens, official accounts and other providers, without editing files;
- Unified provider / Shared Config Snippet carries shared configuration (plugins, MCP) across switches, so switching does not reset your setup;
- Local routing with automatic failover — requests are forwarded through your machine, a failing primary provider switches to a backup, and a circuit breaker stops hammering a broken provider;
- Usage and cost estimation — even without local routing, it tallies usage from each tool’s local session records;
- Endpoint speed tests and balance display, so you are not guessing.
Supported tools
The 10 tools listed in the official docs, with their provider mode:
| Tool | Provider mode |
|---|---|
| Claude Code | Switch |
| Claude Desktop | Switch |
| Codex | Switch |
| Gemini CLI | Switch |
| Grok Build | Switch |
| OpenCode | Coexist |
| OpenClaw | Coexist |
| Hermes | Coexist |
| Pi | Coexist |
| MiniMax Code | Coexist |
- Switch: one provider is active at a time; switching rewrites that tool’s config file.
- Coexist: several providers are written into the tool’s own config at once, and you pick one inside the tool.
Feature support (local routing, aggregation, tray switching, MCP, Skills, prompts, sessions, usage stats) differs per tool — check the official comparison table.
System requirements
| Platform | Minimum | Architecture |
|---|---|---|
| Windows | Windows 10 or newer | x64 / ARM64 |
| macOS | macOS 12 (Monterey) or newer | Intel / Apple Silicon |
| Linux | glibc 2.35+ and WebKitGTK 4.1 | x64 / ARM64 |
On Linux that means Ubuntu 22.04+, Debian 12+ or a recent Fedora; RHEL / Rocky / Alma 8–9 ship system libraries that are too old and are not supported.
Next
- Install cc-switch — per-platform steps
- Configure AllTokens — add the provider and enable it
- No key yet? See Keys and authentication