kaitranntt/ccs

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.

What it solves

CCS (Claude Codex Switch) eliminates the need to manually rewrite configuration files or break active sessions when switching between different AI providers, runtimes, and accounts. It provides a single, stable command surface to manage multiple AI profiles and runtimes seamlessly.

How it works

CCS acts as a manager and proxy. It allows users to switch between various runtimes (like Claude Code, Codex CLI, and Factory Droid) and providers (including OAuth providers like xAI/Grok and Claude, and API/local models like Ollama and llama.cpp). It includes a local Anthropic-compatible proxy that can bridge Claude Code into OpenAI-compatible providers, transforming requests and SSE streams.

Who it’s for

Developers who use multiple AI coding assistants or LLM providers and want a unified way to manage their accounts, subscriptions, and model routing without configuration thrash.

Highlights

  • Multi-Provider Support: Supports a wide range of providers including Claude, Codex, xAI/Grok, GLM, and local models via Ollama.
  • OpenAI-Compatible Routing: Bridges Claude Code to OpenAI-compatible providers via a local proxy.
  • Management Dashboard: Includes a visual dashboard for tracking usage, costs, and session patterns, as well as live auth and health monitoring.
  • macOS Menu Bar Integration: A dedicated companion app (CCS Bar) for monitoring subscription quotas and daily spend.
  • Managed Tooling: Provisions local tools like WebSearch and browser automation for third-party launches.

Related

  • Project
  • Project
  • Project
  • Project
  • Project