farion1231/cc-switch

⭐ 65,650  ·  Rust  ·  GitHub Repo

A cross-platform desktop All-in-One assistant tool for Claude Code, Codex, OpenCode, openclaw & Gemini CLI.

ai-tools claude-code codex desktop-app hermes hermes-agent mcp minimax

1-Sentence Summary

A cross-platform desktop command center unifying all major AI coding CLI tools into one seamless interface.

🔥 Key Capabilities & USP

• Unified Provider Management – Stop juggling terminal windows and config files for Claude Code, Codex, Gemini CLI, OpenCode, and OpenClaw. CC Switch provides a single desktop interface to add, switch, and manage API keys across all providers, eliminating the cognitive overhead of tool fragmentation.
• Centralized Skills Control – Manage AI agent capabilities (enable/disable, organize) from one place instead of per-tool configuration. This is a game-changer for teams standardizing agent behaviors across different coding assistants.
• MCP (Model Context Protocol) Integration – Built-in support for connecting external tools and services via MCP, extending agent capabilities without wrestling with CLI flags or environment variables.
• Cross-Platform Native Experience – Built on Tauri 2 (Rust + TypeScript), delivering native performance on Windows, macOS, and Linux with explicit WSL support for Windows developers working in Linux environments.
• Sponsor/Partner Ecosystem – Integrated access to discounted API relay providers (MiniMax, PackyCode, AIGoCode), reducing operational costs for heavy AI tool users.

USP: CC Switch is the only tool that treats the fragmented AI coding CLI ecosystem as a unified platform, offering provider, skill, and MCP management in a single desktop app.

Technical Architecture

Layer	Technology	Role
Desktop Shell	Rust + Tauri 2	Native window management, system tray, file system access, WSL integration
Frontend	TypeScript (Tauri ecosystem)	UI rendering, state management, user interactions
Provider Layer	Rust (custom)	API key management, provider switching, CLI tool orchestration
Skills Engine	Rust (custom)	Centralized skills enable/disable, capability organization
MCP Integration	Rust (custom)	Model Context Protocol client, external tool connectivity
Platform Support	Windows, macOS, Linux, WSL	Full cross-platform deployment with native performance

Architectural Highlights:

• Native performance via Rust backend (no Electron overhead)
• Secure credential storage through Tauri's native OS keychain integration
• Extensible provider architecture – adding new AI CLI tools is a configuration change, not a code rewrite
• WSL-aware – detects and bridges Windows/Linux environments seamlessly

Quick Start Guide

# 1. Download the latest release for your platform
# Visit: https://github.com/farion1231/cc-switch/releases

# 2. Install (macOS example)
# Drag to Applications folder

# 3. Launch CC Switch and add your API keys
# Claude Code, Codex, Gemini CLI, OpenCode, OpenClaw

# 4. Start switching between providers from the desktop UI
# No more terminal juggling!

Setup Logic:

1. Download the appropriate installer for your OS (Windows .exe, macOS .dmg, Linux .AppImage/.deb)
2. Launch the app and navigate to Provider Management
3. Add API keys for each AI CLI tool you use
4. Configure skills and MCP connections as needed
5. Use the desktop interface to switch providers on the fly

Pros, Cons & Use Cases

Pros

• Eliminates context-switching – One interface for all AI coding assistants
• Native performance – Tauri 2 is significantly lighter than Electron-based alternatives
• Active sponsor ecosystem – Discounted API access through integrated partners
• Multi-language documentation – English, Chinese, and Japanese support
• Open source – Full visibility and community contributions

Cons

• Third-party API relay dependency – Optimal pricing relies on sponsor integrations, which may change
• Separate subscriptions required – You still need individual API keys for each AI tool
• Partner ecosystem lock-in risk – Heavy sponsor integration may create vendor dependency

Who should NOT use this?

• Single-tool users – If you only use one AI coding assistant (e.g., just Claude Code), this adds unnecessary complexity
• CLI purists – Developers who prefer terminal-based workflows and don't need a GUI layer
• Security-sensitive teams – Centralizing API keys in a third-party app may violate strict security policies
• Non-AI coding workflows – Teams not using AI coding assistants will find no value here

Ideal Use Cases

• Multi-tool power users – Developers who switch between Claude Code, Codex, and Gemini CLI daily
• Engineering teams – Standardizing AI agent skills and configurations across team members
• Cross-platform developers – Those working on Windows, macOS, and Linux who need consistent tooling
• Cost-conscious teams – Leveraging sponsor discounts to reduce API costs across multiple tools
• MCP enthusiasts – Developers building agent workflows that integrate external tools via Model Context Protocol

Community & Activity

With 65,650 stars and active development (last updated May 2026), CC Switch has clearly struck a nerve in the AI developer community. This is not a side project – it's a rapidly growing ecosystem with strong momentum. The multi-language documentation (English, Chinese, Japanese) signals a global user base, and the sponsor/partner integrations suggest a sustainable development model. The Tauri 2 architecture positions it well for long-term maintainability and performance. For a project solving such a fresh problem (AI CLI tool fragmentation), this level of adoption is remarkable and indicates strong product-market fit.