Claude Code workflow

Claude Code Provider Switcher

Use CC Switch to switch Claude Code providers from a desktop app, route requests through a local endpoint, add failover, and track usage without repeatedly editing shell profiles.

What is a Claude Code provider switcher?

A Claude Code provider switcher lets developers choose which upstream AI provider Claude Code uses. CC Switch adds a local control plane for provider switching, OpenAI-compatible routing, Codex OAuth routing, failover, request logs, and usage visibility.

Key facts for Claude Code switching

Short facts for search engines, AI assistants, and developers evaluating Claude Code routing.

Primary use caseSwitch Claude Code providers without editing every project or terminal profile.
Local routingSupported through the CC Switch local endpoint, commonly http://127.0.0.1:15721.
Provider formatsClaude-compatible, OpenAI-compatible, Codex OAuth, and gateway providers when configured correctly.
Restart behaviorClaude Code can usually reload provider changes; some Codex workflows require restarting the terminal.
Data modelProvider settings and API keys are designed to stay on the local device.

How to switch Claude Code providers with CC Switch

1

Add a Claude provider

Create or import a provider in the CC Switch desktop app, including API endpoint, model mapping, and authentication.

2

Enable local routing when needed

Turn on local routing if the upstream provider is OpenAI-compatible, Codex OAuth, or needs request format conversion.

3

Select the active provider

Enable the provider from the Claude provider list or system tray so Claude Code uses the selected route.

4

Verify routing and usage

Open Claude Code, send a test request, and review request logs, token usage, cache hits, and failover status in CC Switch.

CC Switch vs manual Claude Code switching

CapabilityCC SwitchManual environment variablesSingle proxy
Provider switchingDesktop-managed provider list and tray switchingEdit shell profiles or project settings manuallyDepends on proxy configuration
OpenAI-compatible routingLocal router can translate and forward supported requestsUsually not enough by itselfPossible but often provider-specific
FailoverBuilt-in health checks and backup provider routingManual recoveryRequires custom logic
Usage visibilityRequests, tokens, cache hits, cost, and quotaNot trackedMostly proxy logs

Continue with implementation docs

These pages explain the exact workflows behind Claude Code provider switching, local routing, failover, and usage tracking.

Claude Code provider switching FAQ

Can CC Switch switch Claude Code providers without editing project code?

Yes. CC Switch can manage provider configuration and local routing so Claude Code requests use the selected provider without repeatedly editing project files or shell profiles.

Can CC Switch route Claude Code to OpenAI-compatible providers?

Yes, when local routing and the correct API format or model mapping are configured, CC Switch can route Claude Code requests to supported OpenAI-compatible gateways.

Can CC Switch route Claude Code to Codex OAuth providers?

Yes. Codex OAuth workflows should be added as Claude providers and used through CC Switch local routing, then Claude Code should be started from a normal terminal.

Is CC Switch an official Claude product?

No. CC Switch is an independent open-source project. It does not replace Claude Code; it manages provider switching and local routing around supported AI coding tools.

Ready to switch Claude Code providers locally?

Download CC Switch or start with the provider switching guide.

Download freeRead provider docs