by kaitranntt
Switch between Claude accounts, Gemini, Copilot, OpenRouter (300+ models) via CLIProxyAPI OAuth proxy. Visual dashboard, remote proxy support, WebSearch fallback. Zero-config to production-ready.
# Add to your Claude Code skills
git clone https://github.com/kaitranntt/ccs
Run Claude, Codex, Droid-routed profiles, GLM, local models, and Anthropic-compatible APIs without config thrash.
Website | Documentation | Product Tour | CLI Reference
CCS gives you one stable command surface while letting you switch between:
The goal is simple: stop rewriting config files, stop breaking active sessions, and move between providers in seconds.
npm install -g @kaitranntt/ccs
ccs config
Then launch whatever runtime fits the task:
ccs
ccs codex
ccs --target droid glm
ccs glm
ccs ollama
No comments yet. Be the first to share your thoughts!
Need the full setup path instead of the short version?
| Need | Start here |
| --- | --- |
| Install and verify CCS | /getting-started/installation |
| First successful session | /getting-started/first-session |
| Visual walkthrough | /getting-started/product-tour |
| Provider selection | /providers/concepts/overview |
| Full command reference | /reference/cli-commands |
| Troubleshooting | /reference/troubleshooting |

Track usage, costs, and session patterns across profiles. Deep dive: Dashboard Analytics.

See auth state, account health, and provider readiness without dropping into raw config. Deep dive: Live Auth Monitor.

Manage OAuth-backed providers, quota visibility, and proxy-wide routing from one place. CCS now surfaces round-robin vs fill-first natively in both CLI and dashboard flows instead of hiding that choice inside raw upstream controls. Deep dive: CLIProxy API.

CCS can provision first-class local tools like WebSearch and image analysis for third-party launches instead of leaving you to wire them by hand. Deep dive: WebSearch.
The README stays short on purpose. The docs site owns the detailed guides and reference material.
| If you want to... | Read this | | --- | --- | | Understand what CCS is and how the pieces fit together | Introduction | | Install CCS cleanly on a new machine | Installation | | Go from install to a successful first run | Your First CCS Session | | See the dashboard and workflow surfaces before setup | Product Tour | | Compare OAuth providers, Claude accounts, and API profiles | Provider Overview | | Learn the dashboard structure and feature pages | Dashboard Overview | | Configure profiles, paths, and environment variables | Configuration | | Keep OpenCode aligned with your live CCS setup | OpenCode Sync Plugin | | Browse every command and flag | CLI Commands | | Recover from install, auth, or provider failures | Troubleshooting | | Understand storage, config, and architecture details | Reference |
# Design with default Claude
ccs "design the auth flow"
# Implement with a different provider
ccs codex "implement the user service"
# Use a cheaper API profile for routine work
ccs glm "clean up tests and docs"
# Run a local model when you need privacy or offline access
ccs ollama "summarize these logs"
| Project | Author | Description | | --- | --- | --- | | opencode-ccs-sync | @JasonLandbridge | Auto-sync CCS providers into OpenCode |