npm install -g @kaitranntt/ccs

yarn global add @kaitranntt/ccs    # yarn
pnpm add -g @kaitranntt/ccs        # pnpm (70% less disk space)
bun add -g @kaitranntt/ccs         # bun (30x faster)

ccs config
# Opens http://localhost:3000

The dashboard provides visual management for all account types:

• Claude Accounts: Create isolated instances (work, personal, client)
• OAuth Providers: One-click auth for Gemini, Codex, Antigravity
• API Profiles: Configure GLM, Kimi with your keys
• Health Monitor: Real-time status across all profiles

Analytics Dashboard

Live Auth Monitor

CLI Proxy API & Copilot Integration

WebSearch Fallback

OpenRouter Integration (v7.0.0): CCS v7.0.0 adds OpenRouter with interactive model picker, dynamic discovery, and tier mapping (opus/sonnet/haiku). Create via ccs api create --preset openrouter or dashboard.

OAuth providers authenticate via browser on first run. Tokens are cached in ~/.ccs/cliproxy/auth/.

Powered by:

• CLIProxyAPIPlus - Extended OAuth proxy with Kiro (@fuko2935, @Ravens2121) and Copilot (@em4go) support
• CLIProxyAPI - Core OAuth proxy for Gemini, Codex, Antigravity
• copilot-api - GitHub Copilot API integration

ccs           # Default Claude session
ccs gemini    # Gemini (OAuth)
ccs codex     # OpenAI Codex (OAuth)
ccs kiro      # Kiro/AWS CodeWhisperer (OAuth)
ccs ghcp      # GitHub Copilot (OAuth device flow)
ccs agy       # Antigravity (OAuth)
ccs glm       # GLM (API key)

Run multiple terminals with different providers:

# Terminal 1: Planning (Claude Pro)
ccs work "design the authentication system"

# Terminal 2: Execution (GLM - cost optimized)
ccs glm "implement the user service from the plan"

# Terminal 3: Review (Gemini)
ccs gemini "review the implementation for security issues"

Create isolated Claude instances for work/personal separation:

ccs auth create work

# Run concurrently in separate terminals
ccs work "implement feature"    # Terminal 1
ccs  "review code"              # Terminal 2 (personal account)

ccs doctor

Verifies: Claude CLI, config files, symlinks, permissions.

ccs update              # Update to latest
ccs update --force      # Force reinstall
ccs update --beta       # Install dev channel

ccs sync

Re-creates symlinks for shared commands, skills, and settings.

CCS auto-creates config on install. Dashboard is the recommended way to manage settings.

Config location: ~/.ccs/config.yaml

export CCS_CLAUDE_PATH="/path/to/claude"              # Unix
$env:CCS_CLAUDE_PATH = "D:\Tools\Claude\claude.exe"   # Windows

Third-party profiles (Gemini, Codex, GLM, etc.) cannot use Anthropic's native WebSearch. CCS automatically provides web search via CLI tools with automatic fallback.

CCS intercepts WebSearch requests and routes them through available CLI tools:

Configure via dashboard (Settings page) or ~/.ccs/config.yaml:

websearch:
  enabled: true                    # Enable/disable (default: true)
  gemini:
    enabled: true                  # Use Gemini CLI (default: true)
    model: gemini-2.5-flash        # Model to use
  opencode:
    enabled: true                  # Use OpenCode as fallback
  grok:
    enabled: false                 # Requires XAI_API_KEY

See docs/websearch.md for detailed configuration and troubleshooting.

CCS v7.x supports connecting to remote CLIProxyAPI instances, enabling:

• Team sharing: One CLIProxyAPI server for multiple developers
• Cost optimization: Centralized API key management
• Network isolation: Keep API credentials on a secure server

Configure via dashboard (Settings > CLIProxy Server) or CLI flags:

ccs gemini --proxy-host 192.168.1.100 --proxy-port 8317
ccs codex --proxy-host proxy.example.com --proxy-protocol https

See Remote Proxy documentation for detailed setup.

npm uninstall -g @kaitranntt/ccs

yarn global remove @kaitranntt/ccs
pnpm remove -g @kaitranntt/ccs
bun remove -g @kaitranntt/ccs

• YAGNI: No features "just in case"
• KISS: Simple, focused implementation
• DRY: One source of truth (config)

See CONTRIBUTING.md.

MIT License - see LICENSE.