CCS - Claude Code 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

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, Copilot, Kiro, Claude, Qwen, Kimi, and more
• API and local-model profiles like GLM, Kimi, OpenRouter, Ollama, llama.cpp, Novita, and Alibaba Coding Plan

The goal is simple: stop rewriting config files, stop breaking active sessions, and move between providers in seconds.

Quick Start

npm install -g @georgedong32/ccs
ccs config

Then launch whatever runtime fits the task:

ccs
ccs codex
ccs --target droid glm
ccs glm
ccs ollama

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 |

See CCS In Action

Usage Analytics

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

Live Auth And Health Monitoring

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

OAuth Provider Control Center

Manage OAuth-backed providers, quota visibility, and routing from one place. Deep dive: CLIProxy API.

Managed Tooling And Fallbacks

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.

Docs Matrix

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 |

Example Workflow

# 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"

Community Projects

| Project | Author | Description | | --- | --- | --- | | opencode-ccs-sync | @JasonLandbridge | Auto-sync CCS providers into OpenCode |

Contribute And Report Safely

• Contributing guide: CONTRIBUTING.md
• Starter work: good first issue, help wanted
• Questions: open a question issue
• Security reports: SECURITY.md and the private advisory form

Star History