# CC Switch

> One desktop app that holds the provider configuration for every coding-agent CLI you run

- Category: AI Coding / Coding-Agent Harnesses & Runtimes
- Language: Rust
- Licence: MIT
- Repository: https://github.com/farion1231/cc-switch
- Website: https://ccswitch.io
- Canonical page: https://ai-tldr.dev/tools/cc-switch/

## In short

CC Switch is One desktop app that holds the provider configuration for every coding-agent CLI you run. CC Switch replaces that with a single desktop application. It sits in the Coding-Agent Harnesses & Runtimes category of the AI Coding tools and is open-source, written in Rust and licensed MIT. To get started: install on macOS.

## Overview

Every coding-agent CLI keeps its own configuration file in its own format, so working across several of them — or pointing one of them at a different provider — means hand-editing dotfiles and restarting terminals. CC Switch replaces that with a single desktop application. It supports eight tools (Claude Code, Claude Desktop, Codex, Gemini CLI, Grok Build, OpenCode, OpenClaw and Hermes Agent), ships more than fifty provider presets, and switches the active provider from the main window or the system tray.

Beyond switching, it runs a local proxy in front of the agents. The proxy converts between request formats, watches provider health and fails over automatically, with a circuit breaker to stop hammering an endpoint that is down. A usage dashboard reports spend, request counts and token totals with trend charts and per-request logs, so the cost of a given provider is visible rather than inferred from a monthly bill.

The app also manages the parts of an agent setup that live outside the provider block. MCP servers are edited in one panel and synced bidirectionally across applications; prompts get a Markdown editor; skills install from GitHub in one click. A session manager browses and restores past conversations, agent files are editable with Markdown preview, and settings sync through Dropbox, OneDrive, iCloud or WebDAV. It is built with Tauri 2 and Rust behind a React front end, and distributed as a native installer rather than an Electron bundle.

## What it does

- Eight supported agent CLIs with 50+ provider presets, one-click switching and a system-tray menu
- Local proxy with request-format conversion, health monitoring, auto-failover and a circuit breaker
- Unified MCP server panel with bidirectional sync across applications
- Markdown prompt editor and one-click skill installation from GitHub
- Usage dashboard: spend, requests and tokens with trend charts and per-request logs
- Session manager for browsing and restoring conversation history
- Settings sync over Dropbox, OneDrive, iCloud or WebDAV, plus deep links and an auto-updater

## Getting started

CC Switch ships as a native desktop installer for Windows, macOS and Linux. The commands below are the ones given in the project README.

1. Install on macOS

   The Homebrew cask is the quickest route; a `.dmg` is also published on the releases page.

```bash
brew install --cask cc-switch
```

2. Install on Arch Linux

   A prebuilt AUR package is maintained for the binary release.

```bash
paru -S cc-switch-bin
```

3. Install on Windows or other Linux distributions

   Download the installer for your platform from the GitHub releases page: `CC-Switch-v{version}-Windows.msi` or a portable `.zip` on Windows, and a `.deb`, `.rpm` or `.AppImage` on Linux.

```text
https://github.com/farion1231/cc-switch/releases
```

4. Add a provider

   Open the app and either pick one of the bundled presets or create a custom provider configuration.

```text
Providers → Add → choose a preset, or fill in a custom endpoint and key
```

5. Switch and apply

   Switch from the main window or the tray icon, then restart the terminal or CLI tool to pick up the change — Claude Code supports hot-switching without a restart. To go back to a vendor's own login, add the official login preset and follow that CLI's OAuth flow.

```text
Tray icon → select provider → restart your CLI (Claude Code switches live)
```

## When to use it

- Reach for it when you run more than one coding-agent CLI and are tired of hand-editing a config file per tool
- Reach for it when you want to move a coding agent between providers without re-authenticating from scratch each time
- Reach for it when a provider's reliability is the problem — the local proxy fails over and trips a circuit breaker for you
- Reach for it when you need per-request visibility into what your agent sessions are actually costing