# Use CC-Switch to configure multiple Coding Agents.

{% hint style="info" %}
This documentation is provided for informational purposes only and demonstrates how to configure and use our API with third-party AI chat interfaces. Any third-party software, websites, or services mentioned are not operated, controlled, or endorsed by us.
{% endhint %}

## Overview

This tutorial guides you through integrating **RouterLink**—WORLD3's decentralized AI model routing infrastructure—with **CC Switch**, the All-in-One Manager for Claude Code, Codex, Gemini CLI, OpenCode, OpenClaw & Hermes.

### What You Will Learn

By completing this tutorial, you will:

* **Configure CC Switch** to connect with RouterLink's API endpoint
* **Authenticate** using your RouterLink API credentials with custom headers
* **Add and manage AI models** available through the RouterLink network
* **Execute inference requests** through CC Switch's conversational interface

### Prerequisites

Before proceeding, ensure you have:

* A RouterLink API key (obtain one from the [Quick Start Guide](https://docs.world3.ai/world3/how-to-guides/routerlink/quick-start-guide))
* A web browser with internet access
* Basic familiarity with API configuration concepts

## Introduction to CC Switch

<figure><img src="/files/7WnCInJX9NBHYWJTJmhH" alt=""><figcaption></figcaption></figure>

[CC Switch](https://github.com/farion1231/cc-switch) gives you a single desktop app to manage all six CLI tools (Claude Code, Codex, Gemini CLI, OpenCode, OpenClaw & Hermes). Instead of editing config files by hand, you get a visual interface to import providers with one click, switch between them instantly, with 50+ built-in provider presets, unified MCP and Skills management, and system tray quick switching — all backed by a reliable SQLite database with atomic writes that protect your configs from corruption.**CC Switch** Key Features:

* One App, Five CLI Tools — Manage Claude Code, Codex, Gemini CLI, OpenCode, and OpenClaw from a single interface
* No More Manual Editing — 50+ provider presets including AWS Bedrock, NVIDIA NIM, and community relays; just pick and switch
* Unified MCP & Skills Management — One panel to manage MCP servers and Skills across four apps with bidirectional sync
* System Tray Quick Switch — Switch providers instantly from the tray menu, no need to open the full app
* Cloud Sync — Sync provider data across devices via Dropbox, OneDrive, iCloud, or WebDAV servers
* Cross-Platform — Native desktop app for Windows, macOS, and Linux, built with Tauri 2
* Built-in Utilities — Includes various utilities for first-launch login confirmation, signature bypass, plugin extension sync, and more

### Step 1: Install CC Switch

* Windows:

Download the latest `CC-Switch-v{version}-Windows.msi` installer or `CC-Switch-v{version}-Windows-Portable.zip` portable version from the [Releases](https://github.com/farion1231/cc-switch/releases) page.

* Windows WSL

CC Switch provides dedicated support for WSL (Windows Subsystem for Linux). After installing CC Switch on a Windows host, you can directly manage configurations of CLI tools like Claude Code within WSL, without needing to install CC Switch separately inside the WSL environment.Once configured, CC Switch bridges network requests between WSL and Windows through a local proxy, enabling unified management.

* macOS

Method 1: Install via Homebrew (Recommended)

```bash
brew tap farion1231/ccswitch
brew install --cask cc-switch
```

Update:

```bash
brew upgrade --cask cc-switch
```

Method 2: Manual DownloadDownload `CC-Switch-v{version}-macOS.dmg` (recommended) or `.zip` from the [Releases](https://github.com/farion1231/cc-switch/releases) page.

> Note: CC Switch for macOS is code-signed and notarized by Apple. You can install and open it directly.

* Arch Linux

Install via paru (Recommended)

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

* Linux

Download the latest Linux build from the [Releases](https://github.com/farion1231/cc-switch/releases) page:

* `CC-Switch-v{version}-Linux.deb` (Debian/Ubuntu)
* `CC-Switch-v{version}-Linux.rpm` (Fedora/RHEL/openSUSE)
* `CC-Switch-v{version}-Linux.AppImage` (Universal)

> Flatpak: Not included in official releases. You can build it yourself from the `.deb` — see [`flatpak/README.md`](https://github.com/farion1231/cc-switch/blob/main/flatpak/README.md) for instructions.

### Step 2: Configure CC Switch

Take configuring Claude Code as an example.Run CC-Switch, select the Claude Code icon, then click the “+” in the top-right corner.

<figure><img src="/files/1Kco8YjIlKnObj4Ak0Ov" alt=""><figcaption></figcaption></figure>

Select "Custom Configuration "

<figure><img src="/files/Ecxftje0AUKtUtG6DzBJ" alt=""><figcaption></figcaption></figure>

Enter the following information.

| Field         | Content                                                                                                           |
| ------------- | ----------------------------------------------------------------------------------------------------------------- |
| Provider Name | Routerlink (Custom)                                                                                               |
| API Key       | Obtain one from the [Quick Start Guide](https://docs.world3.ai/world3/how-to-guides/routerlink/quick-start-guide) |
| API Endpoint  | <https://router-link.world3.ai/api>                                                                               |

<figure><img src="/files/7xbTZMNYv88J7sU89AOa" alt=""><figcaption></figcaption></figure>

Click “Advanced Options” to configure the model.

| Field                | Content                     |
| -------------------- | --------------------------- |
| Main Model           | anthropic/claude-sonnet-4-6 |
| Default Haiku Model  | anthropic/claude-haiku-4-5  |
| Default Sonnet Model | anthropic/claude-sonnet-4-6 |
| Default Opus Model   | anthropic/claude-opus-4-7   |

{% hint style="info" %}
You can replace the model with any model compatible with the Anthropic format.
{% endhint %}

Finally, click “Save.” The configuration will then be complete.

<figure><img src="/files/EaaVhSnUpP28xHOCAPjZ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/zqUPnAihAMSL0xHkhLyH" alt=""><figcaption></figcaption></figure>

Verify the connection. Run in the terminal:

```bash
claude
```

Send a simple conversation request. If the response is normal, it means Routerlink has been successfully connected.

### Step 3: Use it in combination with other coding agent tools.

CC Switch is more than just a manager for Claude Code—it also provides full support for four other mainstream AI coding CLI tools.

* **Using with Codex**&#x20;

OpenAI Codex CLI users can manage Codex provider configurations independently within CC Switch, supporting connections to OpenAI official services, Azure OpenAI, or third-party compatible APIs. There’s no need to manually modify the `OPENAI_API_KEY` environment variable when switching models.

* **Using with Gemini CLI**&#x20;

Google Gemini CLI configurations are relatively scattered. CC Switch consolidates them into a unified interface, supporting quick switching between multiple Google accounts or multiple Gemini API keys. This is especially useful for teams that frequently switch between different projects.

* **Using with OpenCode**&#x20;

OpenCode is an open-source AI coding CLI compatible with multiple providers. CC Switch includes built-in support for OpenCode, allowing you to directly manage its configuration files without the hassle of manually editing TOML/JSON files.

* **Using with OpenClaw**&#x20;

OpenClaw is an open-source CLI tool compatible with the OpenAI API, suitable for advanced users who need custom model routing. The way CC Switch works with OpenClaw:

&#x20; a. Create a separate provider group for OpenClaw within CC Switch

&#x20; b. Configure aggregation platforms such as Routerlink or OpenRouter as upstream providers for OpenClaw

&#x20; c. Use CC Switch’s hot-switching feature to quickly switch between different OpenClaw upstreams

This combination is particularly useful for developers who need to compare response quality across different API providers—switch providers in CC Switch without making any changes on the OpenClaw side.

## Troubleshooting

### How can I make CC Switch work in WSL?

CC Switch is installed on the Windows side and bridges requests from WSL through a local proxy. You just need to ensure that WSL’s proxy settings point to the local listening port of CC Switch. The specific port number can be found in the proxy settings page of CC Switch.

### Do I need to restart Claude Code after switching the provider?

No. CC Switch’s hot-switching feature takes effect immediately after activating a new provider, and the current terminal session does not need to be restarted.

### Where is the configuration data stored?

The local database is stored at `~/.cc-switch/cc-switch.db`, and the settings file is located at `~/.cc-switch/settings.json`. CC Switch automatically keeps the 10 most recent backup versions.

### Can I import someone else’s provider configuration via a URL?

Yes. CC Switch supports Deep Links (the `ccswitch://` protocol). Team members can quickly import a shared provider configuration via a link, making it ideal for unified API management within teams.

### Does CC Switch support AWS Bedrock?

\
Yes. It includes built-in presets for AWS Bedrock and supports cross-region inference, making it suitable for enterprise users who access Claude models through Bedrock.

### Need more help?

Please check the official documentation. <https://github.com/farion1231/cc-switch/blob/main/docs/user-manual/en/README.md#5-faq>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.world3.ai/world3/how-to-guides/routerlink/tutorials/use-cc-switch-to-configure-multiple-coding-agents..md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
