Build a Full-Power AI Coding Setup: Installing CC Switch and Configuring TeamoRouter
CC Switch manages Claude Code, Codex, Gemini CLI and other agent configs from one place, with hot-swappable API routing. This guide walks you through installing CC Switch and connecting it to TeamoRouter, a unified LLM gateway built for agent workloads, so you avoid the runaway bills caused by broken prompt caching.
· cc-switch · claude-code · api-gateway
CC Switch (ccswitch.io) is an open-source desktop control panel built for heavy AI coding users. It manages the configuration of mainstream agent tools, Claude Code, Codex, Gemini CLI, OpenClaw and more, from a single cross-platform app, with hot-swappable API routing, automatic failover, and shared sessions across multiple apps.
In the agent era, though, the quality of your API provider directly determines both the size of your bill and the success rate of your code. Many of the "90% off" budget relay stations on the market rotate through pools of accounts under the hood, which means prompt caching is effectively broken. Because an agent resends a long context on every turn, an API with no caching can blow up your token consumption by 10x, so the real bill ends up higher than paying official list price.
To get the most out of CC Switch, you want to connect it to a unified LLM gateway built natively for agent workloads, TeamoRouter.
Why Agents Need TeamoRouter
Before you start configuring anything, understanding the difference in infrastructure helps you avoid huge hidden costs:
- Genuinely best-in-class value (cache hit rate >99%): TeamoRouter relies on premium upstream channels and low-level optimizations to achieve an extremely high cache hit rate under load (a cache-read request is billed at just 10% of full price). Combined with the platform's real-time floating rates as low as 10–20% of list price, every token goes where it counts.
- 100% agent-protocol compatible: It fully matches every advanced feature of Claude Code and Codex (tool calling and the various beta features). Miss one detail and some agent capability fails silently.
- Enterprise-grade concurrency and availability (SLA 99.6%): Up to 5,000 QPM and tens of millions of TPM, with time-to-first-token (TTFT) close to going direct. When you go to sleep and let an agent refactor your code all night long, what you need is an absolutely stable artery that never quietly downgrades the model.
CC Switch Installation and Configuration Guide
1. Get your TeamoRouter API credentials: a stable power source for your agent
- Visit the TeamoRouter site (https://teamorouter.com).
- Sign up and log in to the dashboard.
- Generate your own
API Keyin the console and note down the officialBase URL. - Enterprise perk (optional): Enterprise users can apply for an enterprise plan in the dashboard for an extra 5% off, multi-tier permissions, budget management, and support for corporate bank transfers and VAT invoices.
2. Download and install CC Switch: works on all major desktop platforms
Grab the latest build from the CC Switch site (ccswitch.io) or its GitHub Releases page.
- Windows: Download the
.msior.exeinstaller, double-click it, and follow the wizard. - macOS: We recommend Homebrew for one-line install and updates:
brew tap farion1231/ccswitch
brew install --cask cc-switch
- Linux: Official
.deb,.rpm, and AppImage builds are provided; Arch Linux users can also install viaparu -S cc-switch-bin.
3. Add TeamoRouter in CC Switch: set it as your global provider
- Launch the CC Switch desktop app.
- Click Provider Management in the left sidebar.
- Click Add Provider and choose the custom OpenAI-compatible or Anthropic-compatible format.
- Fill in the values from step 1:
- Name:
TeamoRouteris a good choice. - Base URL: the gateway address TeamoRouter gave you.
- API Key: your personal key.
- Name:
- Click Save. CC Switch's built-in provider health check will automatically verify that the endpoint is reachable.
4. Route requests through TeamoRouter: apply the config and start vibe coding
- In the CC Switch top navigation bar, pick the agent tool you're using (for example Claude Code, Codex, or OpenCode).
- On that tool's config page, use the dropdown to switch the default provider to the TeamoRouter entry you just added.
- How it takes effect: For Claude Code, CC Switch supports hot switching, so it applies immediately. For most other CLI tools, restart the tool in your terminal to load the new environment variables and config.
If you'd rather skip the desktop app and wire Claude Code to TeamoRouter straight from the command line, see the Claude Code setup guide; to understand how relay stations differ from a direct gateway, read How to Choose a Claude Code Relay Station (and Avoid the Traps).
FAQ
I already have a cheap relay station. Does switching to TeamoRouter really make a difference?
It makes a huge difference. The biggest trap with ordinary relay stations is being cheap on the sticker but having no caching. Agent workflows lean heavily on resubmitting long contexts in a loop, and losing official-grade prompt caching can multiply your token consumption by more than ten times. TeamoRouter runs its own quality-control system that screens out shady suppliers and guarantees a very high cache hit rate, giving you a genuine "low-cost loop."
Is TeamoRouter suitable for teams and enterprises?
Very much so. TeamoRouter is built for efficiency-minded companies and professionals. It ships with a free visual enterprise admin console where you can configure department and per-person permissions, do fine-grained budget control, and audit usage. Enterprise users also get higher routing priority during peak hours, so the business never stalls.
Once configured, can I sync CC Switch across multiple machines?
Yes. CC Switch can export a backup bundle of all provider configs, MCP server settings, and app preferences. Configure TeamoRouter and its dependencies once on one machine, export the config file, then import it on the new machine.