You use multiple AI coding tools
Manage Claude Code, Claude Desktop, Codex, Gemini CLI, OpenCode, OpenClaw, and Hermes Agent from one interface.
Compare CC Switch with manual provider switching and API proxy scripts
Use this page to decide whether CC Switch, manual environment variables, a single API proxy, or custom scripts fit your AI coding workflow.
Quick comparison
The practical difference is not only provider switching. CC Switch also combines local routing, failover, usage tracking, and extension management in one desktop app.
| Capability | CC Switch | Manual env vars | Single API proxy | Custom scripts |
|---|---|---|---|---|
| Multi-app provider switching | Built for seven AI coding apps | Usually one shell or project at a time | Depends on proxy support | Requires maintenance |
| Local routing control | Desktop-managed local endpoint | No central routing layer | Proxy-specific behavior | Possible but fragile |
| Failover and health checks | Built-in routing failover | Manual recovery | Varies by proxy | Must be implemented |
| Usage and quota visibility | Requests, tokens, cost, quota, and cache hits | Not tracked | Often limited to proxy logs | Must be built |
| MCP, Skills, Prompts, sessions | Managed from the same app | Separate files and tools | Usually out of scope | Requires custom glue |
| Credential storage | Local app data store | Shell profiles or env files | Proxy config | Script-specific |
When to use CC Switch
You need local routing control
Route requests through a local endpoint for format conversion, provider switching, failover, and logs.
You care about usage visibility
Track requests, tokens, cache hits, cost, quota, and model pricing without building a dashboard yourself.
When a simpler setup may be enough
Manual environment variables or a single proxy can be enough for one provider, one app, or a temporary experiment. CC Switch is more useful once you need repeatable routing across tools, providers, and sessions.
Continue with implementation docs
These pages explain the provider switching, routing, failover, and usage workflows behind the comparison.
Popular workflow
Switch Provider
Choose the active provider for supported AI coding tools.
Popular workflowLocal Routing Service
Run a local routing endpoint for format conversion and request control.
Popular workflowApplication Routing
Route each coding app to the provider that fits its workflow.
Popular workflowProvider Failover
Keep requests moving when a primary provider fails.
Popular workflowUsage Statistics
Track requests, tokens, cache hits, cost, and quota.
Popular workflowFAQ
Find quick answers for setup, routing, and provider behavior.
Comparison FAQ
What is CC Switch?
CC Switch is an open-source desktop control center for AI coding tools. It helps developers switch AI providers, route requests locally, track usage, and manage MCP, Skills, Prompts, and sessions across supported coding apps.
Does CC Switch replace Claude Code?
No. CC Switch is not an official Claude product and does not replace Claude Code. It manages provider configuration and local routing for tools such as Claude Code, Claude Desktop, Codex, Gemini CLI, OpenCode, OpenClaw, and Hermes Agent.
How does local routing work?
CC Switch runs a local routing service that can translate request formats, select the active provider, apply failover rules, and record request and usage data before forwarding traffic to the provider you configured.
Where are API keys stored?
Provider settings and API keys are stored locally on your device in the CC Switch data store. CC Switch does not host or sell model-provider credentials.
Ready to control AI coding providers locally?
Download CC Switch or start with the provider switching documentation.
Download freeRead provider docs