CCS - Claude Codex Switch
The multi-provider profile and runtime manager for Claude Code and compatible CLIs
Run Claude, Codex, Droid-routed profiles, GLM, local models, and
Anthropic-compatible APIs without config thrash.
Website |
Documentation |
Product Tour |
CLI Reference
[Docker] ghcr.io/kaitranntt/ccs-dashboard:latest is deprecated. Use ghcr.io/kaitranntt/ccs:latest instead. See #1251 and docker/README.md for migration details. To wire a sibling container to CLIProxy, see Connect your app to CLIProxy.
Quick Start (Docker)
With Docker installed:
curl -fsSL https://ccs.kaitran.ca/docker-compose.yaml -o docker-compose.yaml
docker compose up -d
Dashboard at http://localhost:3000 · CLIProxy at http://localhost:8317.
Need a corporate-proxy alternative? Download directly:
https://raw.githubusercontent.com/kaitranntt/ccs/main/docker/compose.yaml
Install on Host (npm)
npm install -g @kaitranntt/ccs
ccs config
Then launch whatever runtime fits the task:
ccs
ccs codex
ccs xai # Alias: ccs grok
ccs --target droid glm
ccs glm
ccs ollama
Why CCS
CCS gives you one stable command surface while letting you switch between:
- multiple runtimes such as Claude Code, Factory Droid, and Codex CLI
- multiple Claude subscriptions and isolated account contexts
- OAuth providers like Codex, xAI/Grok, Kiro, Claude, Kimi, and more, with legacy
Copilot compatibility for existing setups
- API and local-model profiles like GLM, Kimi, OpenRouter, Requesty,
Atlas Cloud, Cheaper Inference, OrcaRouter, Runcrate, Obscurify.ai,
CloudGPU, Ollama, llama.cpp, Novita, Fireworks AI, and QwenCloud Coding Plan
Qwen Code account linking is not available in the bundled CLIProxy runtime yet;
use an API-key Qwen profile such as QwenCloud Coding Plan for Qwen models.
The goal is simple: stop rewriting config files, stop breaking active sessions,
and move between providers in seconds.
OpenAI-Compatible Routing
CCS can now bridge Claude Code into OpenAI-compatible providers through a local
Anthropic-compatible proxy instead of requiring a native Anthropic upstream.
ccs api create --preset hf
ccs hf
Need to manage the proxy manually?
ccs proxy start hf
eval "$(ccs proxy activate)"
The proxy also supports request-time profile:model selectors, scenario-based
model routing through proxy.routing, and explicit activation helpers such as
ccs proxy activate --fish.
Guide:
OpenAI-Compatible Provider Routing.
API Route custom profile
API Route serves an Anthropic-compatible Messages endpoint. Create a custom Claude Code profile and enter your API Route key when prompted:
ccs api create api-route --base-url https://global.api-route.com --model claude-haiku-4-5 --target claude
ccs api-route
Use the host without /v1, since Claude Code appends /v1/messages. Replace the example model with a Claude model ID available to your key; authenticated GET https://global.api-route.com/v1/models lists the IDs. API Route is a paid hosted service: see API keys and pricing. Profile settings use the existing CCS configuration workflow.
Related Project: claude-code-router
claude-code-router is an
excellent standalone tool for routing Claude Code requests to OpenAI-compatible
providers. CCS's local proxy and SSE transformation work was directly informed
by CCR's transformer architecture.
Use CCR when you want a standalone router without CCS profile management.
Use CCS when you want the routing flow integrated with CCS profiles, runtime
bridges, and the existing ccs command surface.
Need the full setup path instead of the short version?
See CCS In Action
CCS Bar For macOS
CCS Bar puts live subscription quota, daily spend, and account controls in the
macOS menu bar. Install it with ccs bar install, launch it with ccs bar, and
tell us what would make it more useful: issues and ideas are welcome in
GitHub Issues.
Deep dive: CCS Bar.
Usage Analytics
This is the beginning of the README. Read the rest at the original. Read the full README ↗
