
Open-source desktop app for managing...
After installing, add a provider on that tool's page, fill the key from a preset when one exists, and enable it instead of hand-editing each tool's config format. Local routing converts formats, switches without a full rewrite, and fails over to a backup when the main provider fails, with a circuit breaker to limit repeated retries. Usage stats still total tokens and cache hits from local session logs when routing is off. Skills, prompts, and sessions can be installed or restored from the same panels. Keys stay in the local database unless you turn on sync to storage you own. It fits developers who use several coding assistants and change API providers often.
CC Switch is an open-source desktop app for managing provider settings of several AI coding tools. The site says it covers ten tools, and it distinguishes a switch mode that enables one provider at a time from a coexist mode that writes several providers into the tool. The interface can add a provider from a preset, test endpoint speed, and show usage and balance. It also manages extension servers, prompts, skills, and sessions. Local routing converts among several API formats and fails over when the main provider fails. Settings stay in a local database by default, with optional sync to storage you configure. The download page says it is open source and free of charge.
Difficulty: Intermediate
Add a provider from a preset
Pick a preset, enter the key, and enable it. The docs say this avoids hand-editing each tool's config file and keeps the previous config.
Local routing and failover
Local routing converts requests among several API formats, switches to a backup when the main provider fails, and uses a circuit breaker to limit retries.
Usage from local sessions
Even with local routing off, token use, cache hits, and spend can be totaled from each tool's local session logs and filtered by date.
Skills, prompts, and sessions
The same app manages extension servers, system prompts, and skills, and it can browse or search session history and copy a resume command.
Local storage with optional sync
Providers and keys stay in a local database unless you enable sync to storage you configure yourself.
Switch among API providers
A developer keeps several providers for one coding tool and switches from the window or the tray instead of opening the config file.
Fail over when the main API fails
With local routing on, a failed main provider is replaced by a backup, and request logs remain for later review.
Check usage from local sessions
Without routing, token and cache figures from each tool's sessions can still be filtered by date to review your own calls.
No. It manages provider settings, extension servers, prompts, skills, and sessions for those tools. The coding tools themselves still have to be installed. The docs split tools into switch and coexist: switch enables one provider at a time and rewrites the config; coexist writes several providers and you pick inside the tool. Routing, tray, and usage support also differ by tool, so check the screen for that tool.
The docs say settings and keys stay in a local database by default. Data is uploaded only if you turn on sync and enter your own network drive or object storage. With sync off, switching providers and reading usage stay on the machine. If local routing is on, requests pass through CC Switch on that machine before they are forwarded, which is separate from handing the key to a third-party account.
Real reviews and feedback from users