A CLI remote control for six AI coding assistants

What it does

cc-switch is a Rust CLI that centralizes provider configs, MCP servers, system prompts, and proxy routes across Claude Code, Codex, Gemini CLI, OpenCode, Hermes, and OpenClaw. Instead of hand-editing scattered JSON and TOML files, you switch contexts through menus or one-liners. It also syncs state via WebDAV, so your setup can follow you across machines.

The interesting bit

The project is a CLI fork of the upstream CC-Switch, but the WebDAV sync remains compatible — meaning you could theoretically mix the TUI and CLI versions without them fighting over state. The --app flag scopes every command to a specific assistant, so cc-switch --app codex mcp sync and cc-switch --app claude mcp sync hit different live configs without cross-contamination.

Key highlights

• Manages API keys, endpoints, and model lists for six AI CLI tools through a single interface
• MCP server lifecycle (add, enable, sync) with stdio/http/sse transport support and per-app targeting
• Prompt preset manager that maps to each app’s convention — CLAUDE.md, AGENTS.md, GEMINI.md, etc.
• Built-in diagnostics: provider speed tests, stream health checks, and local environment tooling audits
• Cross-platform Rust binary with musl and glibc Linux builds, plus a universal macOS binary

Caveats

• The README is heavy on sponsor content (four API relay services with discount codes), which dominates the visual real estate
• Some features like “skills” management are mentioned in the tagline but not detailed in the visible documentation
• Homebrew and built-in update mechanisms conflict; the docs explicitly warn against mixing them

Verdict

Worth a look if you regularly switch between Claude Code and Codex (or their less-famous siblings) and want one source of truth for keys, prompts, and MCP servers. Probably overkill if you only use one assistant, or if you already have a dotfiles repo that handles this via symlinks.