VividKit Crystal clear AI coding
VI
What is ClaudeKit? ClaudeKit CLI Guide Command Finder Commands Cheat Sheet Workflow Recipes CLI Quick Reference Claude Mechanics Permission Modes ClaudeKit Hooks Coexistence Accounts Switcher IDE Config Remote Control Codex App ClaudeKit x Codex Migrate to Other Tools Session Recovery Fix from Logs UI/UX Guide How ClaudeKit Works Inside ClaudeKit

CCS - Claude Code Switch

One command, zero downtime, any provider

Switch between Claude, Codex, Kiro, GLM, Kimi, Ollama and more. Multiple accounts, multiple runtimes — no config thrash.

Created by @kaitranntt

Why CCS?

You're paying for multiple AI subscriptions — Claude Pro, ChatGPT Plus, Z.AI, Kimi, and more — and you want to drive them all from Claude Code CLI without rewriting config files every time you switch.

claude icon Claude Pro openai icon ChatGPT Plus / Codex zai icon Z.AI / GLM kimi icon Kimi minimax icon MiniMax qwen icon Alibaba Coding Plan
Without CCS
Rate limits kill momentum

Hit the cap mid-session and your context, progress, everything stalls.

Switching means rewriting

New settings JSON, edit cliproxy config.yaml, restart Claude Code — every single time.

Each provider, its own setup

Separate auth tokens, config sections, and CLAUDE_CONFIG_DIR for account isolation.

With CCS
One named profile per stack

Switch providers with ccs <profile> — no env vars, no config editing.

Resume across providers

Hit a rate limit? Continue the same task in another provider with --resume.

Auth + config managed

OAuth tokens, account isolation, and runtime adapters handled for you.

Install in 2 commands: v8.2.0 
npm install -g @kaitranntt/ccs && ccs config

Opens the dashboard at http://localhost:3000 — add a provider there, then run ccs <profile> from terminal.

CLI Cheatsheet Provider Decision Tree Best Workflows

Want to learn more about resuming sessions across providers? See the Session Recovery Guide.

Key Features

What sets CCS apart from alternatives

CLI-First

One-Command Switching

Switch providers with named profiles — just ccs <provider>. No env vars, no config editing.

Exclusive

Session Recovery

Resume rate-limited sessions with a different provider. A rare capability across CLI tools.

Multi-Runtime

Bridges Claude Code, Codex CLI (transient credentials), and Factory Droid (multi-target adapter) — one tool, three runtimes.

WebSearch & Browser

Built-in WebSearch and browser automation provisioning for third-party providers.

OpenAI-Compatible Proxy

Local proxy with profile:model selectors and scenario-based routing for any OpenAI-compatible client.

20+ Providers, 3 Auth Tiers

14 CLIProxy OAuth providers, multi-account Claude, and BYO-key API profiles (Alibaba, MiniMax, Novita, Ollama, Llama.cpp).

Extended Thinking

Unified --thinking flag controls reasoning budgets (100K max) across Anthropic, Antigravity, Gemini hybrid, and Codex levels.

Account Safety

Cross-provider isolation, ban detection, and quota monitoring to protect Google accounts when running multiple OAuth providers.

Image & PDF Analysis

MCP-first vision support for third-party launches (GLM/Kimi/Qwen) that lack native image and PDF understanding.

Full Documentation

Dedicated docs site with product tour, CLI reference, and provider-specific guides.

Visual Dashboard

React 19 dashboard for auth monitoring, usage analytics, and profile management.

1

CLI Cheatsheet

@kaitranntt/ccs@8.2.0

Comprehensive reference covering every public root command and subcommand. Grouped by purpose.

Synced 2026-06-08

01 Basics ·7 02 Profile Management ·15 03 Configuration ·5 04 CLIProxy ·16 05 Operations ·14 06 Runtime Targets ·12 07 Docker ·8
01

Basics

7 commands

Route Claude Code through a provider profile.

  • ccs Default profile (Claude Pro/Max)
  • ccs <profile> Run with any named profile
  • ccs glm Z.AI / GLM (cheap coder)
  • ccs kimi Moonshot Kimi (long context)
  • ccs codex OpenAI Codex (Plus/Pro)
  • ccs <profile> "<prompt>" One-shot prompt (no REPL)
  • ccs setup First-time setup wizard
02

Profile Management

15 commands

Create, list, and switch OAuth accounts and API-key profiles.

  • ccs auth create <profile> Create OAuth-based profile
  • ccs auth list List concurrent Claude accounts
  • ccs auth show <profile> Show details of an auth profile
  • ccs auth default <profile> Set default account for a profile
  • ccs auth reset-default Reset default account for a profile
  • ccs auth backup Backup current auth profiles
  • ccs auth resources Inspect profile resource files
  • ccs auth remove <profile> Remove an auth profile
  • ccs api create --preset <name> Create API-key profile (preset)
  • ccs api list List configured API profiles
  • ccs api discover Auto-discover API profiles from env
  • ccs api copy <name> Duplicate an existing API profile
  • ccs api export <name> Export an API profile to a file
  • ccs api import <file> Import an API profile from a file
  • ccs api remove <name> Remove an API profile
03

Configuration

5 commands

Open the dashboard and configure global settings.

  • ccs config Open web dashboard in browser
  • ccs config auth Configure dashboard HTTP Basic Auth
  • ccs config channels Configure official channels (Telegram / Discord / iMessage)
  • ccs config thinking Configure reasoning effort
  • ccs config image-analysis Configure MCP-based image analysis
04

CLIProxy

16 commands

Manage CLIProxy variants, routing, quota, and local lifecycle.

  • ccs cliproxy create Create a new CLIProxy variant
  • ccs cliproxy edit Edit a CLIProxy variant config
  • ccs cliproxy list List CLIProxy variants
  • ccs cliproxy default <variant> Set default CLIProxy variant
  • ccs cliproxy routing Inspect or edit model routing rules
  • ccs cliproxy catalog Show CLIProxy model catalog
  • ccs cliproxy sync Sync CLIProxy config to disk
  • ccs cliproxy quota Inspect provider quota usage
  • ccs cliproxy start Start CLIProxy instance
  • ccs cliproxy restart Restart CLIProxy instance
  • ccs cliproxy stop Stop CLIProxy instance
  • ccs cliproxy status Show CLIProxy status
  • ccs cliproxy doctor Diagnose CLIProxy health
  • ccs cliproxy pause Pause CLIProxy without stopping
  • ccs cliproxy resume Resume a paused CLIProxy
  • ccs cliproxy remove Remove a CLIProxy variant
05

Operations

14 commands

Health checks, lifecycle, tokens, and meta commands.

  • ccs doctor Health check (auth + tokens + paths)
  • ccs persist Lock current profile to ~/.claude
  • ccs migrate Migrate from older configs
  • ccs cleanup Remove unused profiles + caches
  • ccs update Update CCS to latest version
  • ccs sync Sync delegation commands and skills
  • ccs env <profile> Export profile env for third-party tools
  • ccs tokens Manage CLIProxy auth tokens
  • ccs proxy start Start OpenAI-compatible local proxy
  • ccs proxy stop Stop local proxy daemon
  • ccs proxy status Show local proxy status
  • ccs proxy activate Activate proxy for current shell
  • ccs help <topic> Show help for a topic (profiles, providers, targets…)
  • ccs --version Show installed CCS version
06

Runtime Targets

12 commands

Send a profile to a different agent runtime.

  • ccs --target droid <profile> Route profile to Factory Droid runtime
  • ccs --target codex <profile> Route profile to Codex runtime
  • ccs --target claude <profile> Force Claude target (default)
  • ccs-droid <profile> Factory Droid wrapper
  • ccsd <profile> Short alias for ccs-droid
  • ccs-codex <profile> Native Codex CLI wrapper
  • ccsx <profile> Short alias for ccs-codex
  • ccsxp <profile> Codex-on-Codex shortcut
  • ccs browser Claude Browser Attach + Codex Browser Tools
  • ccs cursor Cursor IDE integration
  • ccs copilot GitHub Copilot bridge (deprecated)
  • ccs help completion Shell completion install & testing
07

Docker

8 commands

Run CCS inside a sandboxed container.

  • ccs docker up Start CCS container
  • ccs docker down Stop CCS container
  • ccs docker status Show container status
  • ccs docker logs Tail container logs
  • ccs docker update Update Docker stack image
  • ccs docker config Inspect or edit Docker stack config
  • ccs docker show-key Show current Docker API key (8.1.0+)
  • ccs docker finalize-key-rotation Finalize Docker key rotation (8.1.0+)

Run any command with --help for full options. For detailed setup of a specific profile (Claude / Codex / GLM / Kimi / Gemini …), see the Provider Decision Tree below. Full docs at docs.ccs.kaitran.ca.

2

Configure Your Providers

Choose how you want to set up your AI providers. Pick the method that works best for you.

Provider Decision Tree

Select the provider whose subscription you want to use in Claude Code CLI.

This decision tree is for Claude Code CLI usage only. Web app and desktop app users do not need CCS.

CCS lets you switch between provider subscriptions directly in Claude Code CLI. Pick your provider below to see the exact env vars and config needed.

Anthropic
OpenAI
Google
Cloud AI
IDE & DevTools
Self-Hosted
Which provider do you use? 2 modes Anthropic Plus / Pro OpenAI ⚠ Ban Risk Google 8 providers Cloud AI 7 providers IDE & DevTools 3 providers Self-Hosted Native OAuth Claude Multi-account Claude Pool GPT-5.4 Codex Multi-model ⚠ Antigravity OAuth ⚠ Gemini AWS Pro Kiro Moonshot OAuth Kimi API Key Kimi Direct ~79% cheaper Z.AI / GLM Alibaba OAuth Qwen M2.1 API MiniMax API Key Alibaba Coding DeepSeek + more Novita AI Device Code GitHub Copilot Plus Cursor Plus GitLab Duo Plus CodeBuddy Plus Kilo Free tier iFlow Plus Qoder localhost:11434 Ollama API Key Ollama Cloud localhost:8080 llama.cpp

Click any provider node to see config. Wheel to zoom, drag to pan.

Web Dashboard

New

CCS ships a routed React 19 dashboard organized into workspaces — not a single settings modal. Each workspace targets a specific orchestration concern.

Profiles

Create API profiles for OpenRouter, Alibaba Coding Plan, local runtimes, or custom endpoints.

CLIProxy Plus

Connect OAuth providers, inspect provider status, and tune routing for the local proxy.

Accounts

Create named auth accounts, copy safe commands, and manage shared or isolated context lanes.

Analytics

Read usage by time range so non-technical readers can spot spikes and provider mix quickly.

Health

Run the same checks as ccs doctor and see what needs attention before starting work.

Settings

Configure search, browser, image, proxy, auth, backup, env, and thinking behavior in one place.

Launch Dashboard

Open dashboard (auto-opens browser)

ccs config

Specify custom port

ccs config --port 3000

The dashboard will automatically open in your browser. If not, access it manually at http://localhost:PORT

Beginner setup path

1
Open the local app
ccs config

Start with the dashboard instead of editing YAML by hand.

2
Pick an API profile lane
/providers

Use Profiles for OpenRouter, Alibaba Coding Plan, local models, and custom OpenAI-compatible endpoints.

3
Connect OAuth providers
/cliproxy

Use CLIProxy for Gemini, Codex, Antigravity, Qwen, Claude, Kimi, and related OAuth-backed providers.

4
Verify before coding
/health

Open Health for checks, then Logs when a request fails or a provider returns 404, 429, or 503.

Where to go in the dashboard

Home
/

Quick status cards, account monitor, request distribution, and a shortcut to the dedicated Logs workspace.

Analytics
/analytics

Track token usage, cache cost, model spend, sampled sessions, and time ranges like 24H, 7D, Month, or All Time.

Profiles
/providers

Best first stop for API-key providers and custom endpoints. Create, import, or discover API profiles here.

CLIProxy Overview
/cliproxy

See OAuth provider connection status, quick setup, provider cards, routing mode, session affinity, and model presets.

AI Providers
/cliproxy/ai-providers

Configure CLIProxy Plus provider families, hybrid/API-key connectors, routing behavior, and proxy sync state.

Control Panel
/cliproxy/control-panel

Use when you need proxy lifecycle controls or operational actions around the local CLIProxy service.

Accounts
/accounts

Create auth accounts, manage shared resources, and choose whether an account keeps isolated or shared context.

Shared Resources
/shared

Inspect commands, skills, agents, plugins, settings, and resource policies inherited by shared accounts.

Claude Extension
/claude-extension

Save IDE bindings, verify drift, and apply or reset shared Claude settings plus IDE-local settings.

Codex CLI
/codex

Check detected Codex install, aliases, cliproxy shortcuts, config.toml path, and raw native Codex config.

Factory Droid
/droid

Review and edit Droid BYOK settings in ~/.factory/settings.json, including custom models and defaults.

GitHub Copilot
/copilot

Deprecated compatibility bridge for Copilot model mappings and daemon setup. Prefer newer CLIProxy paths when possible.

Cursor IDE
/legacy/cursor

Legacy Cursor bridge for old local daemon flows. New setups should use CLIProxy-backed Cursor auth.

Health
/health

Run ccs doctor checks across system, environment, config, delegation, OAuth readiness, and WebSearch.

Logs
/logs

Filter live activity, entries, traces, errors, request IDs, JSON payloads, and source-level request details.

Settings
/settings

Configure search backends, browser/image tools, channels, env, thinking, proxy, auth, backup, and raw config.yaml.

Dashboard Preview

CCS Dashboard - Light Mode
Plain-English rule

If you pay for an API key, start in Profiles. If you log in through a provider account, start in CLIProxy or Accounts. If something breaks, go to Health first, then Logs.

Local and inspectable

The dashboard runs on localhost and keeps data on your machine. Sensitive values stay hidden until you explicitly reveal them.

The sidebar groups pages into General (Home, Analytics), Identity & Access (Profiles, CLIProxy, Accounts), Compatible CLIs (Claude Extension, Codex CLI, Factory Droid), Deprecated integrations, and System (Health, Logs, Settings).

3

Best workflows with CCS & ClaudeKit

Curated recipes for routing tasks across providers and runtimes — optimize for cost, depth, or context.

Cost-optimized full cycle

When you want quality planning + review but cheap bulk implementation.

1
# Plan with default Claude (best reasoning)
$ ccs "/ck:plan add payment integration"
2
# Implement with GLM or Qwen (cheap, fast)
$ ccs glm "/ck:cook implement Stripe payment flow"
3
# Run tests with GLM or Qwen (still cheap)
$ ccs glm "/ck:test run payment tests"
4
# Final review with Claude (catches subtle issues)
$ ccs "/ck:code-review check payment implementation"

Deep debugging with thinking models

When a flaky test or subtle bug needs careful reasoning across files.

1
# Investigate root cause with Codex (deep thinker)
$ ccsx codex "$ck:debug investigate flaky webhook test"
2
# Cross-reference call sites with default Claude
$ ccs "/ck:scout cross-reference call sites"
3
# Apply fix with GLM or Qwen (cheap iteration)
$ ccs glm "/ck:fix apply patch + rerun tests"

Multi-runtime routing

When you want to combine Claude Code, Codex, and Droid in one task.

1
# Plan in Claude Code (default runtime)
$ ccs "/ck:plan refactor auth module"
2
# Scaffold via Codex (ccsx)
$ ccsx codex "$ck:cook scaffold module"
3
# Run integration tests in Droid (ccsd) with GLM
$ ccsd glm "/ck:test run integration suite"
4
# Final code review back in Claude Code
$ ccs "/ck:code-review final pass"

Mix providers per step: use a strong reasoning model (Claude / Codex) for planning & review, a cheaper coder (GLM / Qwen) for bulk implementation & tests. Switch runtimes (ccsd, ccsx) when you need a different agent.