CCS
CCS - Claude Codex Switch
A CLI that switches Claude Code between accounts, providers and local models without editing configs
Install
npm install -g @kaitranntt/ccs
ccs configThis is third-party code. Review the repository files before installing.
What it does
CCS stores profiles and launches the right runtime with one command: ccs for Claude, ccs codex, ccs glm, ccs ollama and more. It keeps several Claude subscriptions in isolated contexts, connects OAuth providers through the bundled CLIProxy and API-key profiles such as OpenRouter or GLM. A local Anthropic-compatible proxy lets Claude Code talk to OpenAI-style providers. A web dashboard manages profiles, and it can run in Docker.
Who it is for. For developers who use Claude Code with several accounts or want to plug other models into it.
Good fit when
- You need to switch between work and personal Claude accounts without breaking sessions
- You want to run Claude Code on GLM, Kimi, OpenRouter or a local model
- You need to swap providers per task quickly
Not a fit when
- One account and one model are enough
- Company policy forbids a proxy between the agent and the provider
Example request
Set up a CCS profile for GLM and launch Claude Code with itLimitations
Requires Node.js or Docker. Cloud providers need their own accounts and keys; the Anthropic and OpenAI APIs are unreachable from Russia without a VPN, while local models via Ollama work offline. Using multiple subscriptions and OAuth proxying may conflict with provider terms. Qwen Code account linking is not supported yet.
How to disable. Remove the package with npm uninstall -g @kaitranntt/ccs or stop the containers with docker compose down.
Security check
- Stores OAuth tokens and API keys for several providers
- Proxies all agent traffic through a local server
README in short
The README opens with a Docker Compose quick start and npm install. It explains what CCS switches between: Claude Code, Droid and Codex runtimes, Claude subscriptions, OAuth providers and API-key profiles. A section covers routing to OpenAI-compatible providers through a local proxy and compares it with claude-code-router. Docs are at docs.ccs.kaitran.ca. MIT licensed.
FAQ
How does CCS differ from claude-code-router?
Per the README, claude-code-router is a standalone router, while CCS adds profile management and a single ccs command on top of similar routing.
Can it run in Docker?
Yes, the README provides docker-compose; the dashboard is on port 3000 and CLIProxy on 8317.
Related
Open-source personal AI assistant on your own machine: answers in Telegram, Slack, Discord and WhatsApp, extended with skills and plugins
A self-improving agent from Nous Research with a TUI, messaging gateway, cron jobs and skills it writes itself
An open source coding agent for the terminal and desktop with build and plan modes
Open prompt library with a Claude Code plugin, MCP server and CLI: search, fetch and improve prompts and skills from an agent