CC Switch
Connect CC Switch to Yolo Router and manage providers for Codex, Claude Code, and other CLI tools.
- CC Switch is installed and can open normally.
- The CLI tool you want to manage is installed, such as Codex CLI, Claude Code, Gemini CLI, OpenCode, or OpenClaw.
- A working Yolo Router endpoint, for example
https://api.yolorouter.com. - A Yolo Router API Key generated from the console.
- The model ID you want to use, for example
deepseek-v4-pro. It must exactly match the model ID in the Yolo Router console.
CC Switch manages providers by writing them into each target CLI's config file. Endpoint URL format depends on the selected App: Codex and OpenAI-compatible tools usually use a Base URL with
/v1, while Claude Code usually uses the root endpoint.
Setup
Verify Yolo Router first
Before configuring CC Switch, verify that the API Key, endpoint, and model ID work.
export YOLOROUTER_API_KEY="sk-yolo-..."
curl https://api.yolorouter.com/v1/models \
-H "Authorization: Bearer $YOLOROUTER_API_KEY"$env:YOLOROUTER_API_KEY = "sk-yolo-..."
curl.exe https://api.yolorouter.com/v1/models `
-H "Authorization: Bearer $env:YOLOROUTER_API_KEY"If the model list is returned, confirm that the model ID you plan to use in CC Switch exists, for example deepseek-v4-pro.
Open the target App page
Open CC Switch and select the target App from the top navigation, for example:
CodexClaudeGeminiOpenCodeOpenClaw
Choose Codex if you are configuring Codex CLI. Choose Claude if you are configuring Claude Code.
Add a Provider
Click the + button in the top-right corner to open the Add Provider panel.
Choose App-specific Provider if only the current App should use this provider. Choose Universal Provider if you want multiple Apps to share it.
Use custom configuration and fill in:
Name: for exampleYolo RouterAPI Key: your Yolo Router API KeyEndpoint URL: choose the format in the next step
Enter the Endpoint URL
Use the format that matches the App you are configuring:
| App | Endpoint URL |
|---|---|
| Codex | https://api.yolorouter.com/v1 |
| OpenCode / OpenClaw | https://api.yolorouter.com/v1 |
| Claude Code | https://api.yolorouter.com |
| Gemini CLI | https://api.yolorouter.com |
Do not add a trailing /. Use https://api.yolorouter.com/v1, not https://api.yolorouter.com/v1/.
Fetch or enter the model ID
Make sure that the API Key and Endpoint URL have been filled in. Then, expand the Advanced Options and click Get Model List. CC Switch will use the current key to request the OpenAI-compatible /v1/models interface.
If models are fetched successfully, select the target model from the dropdown.
If fetching fails, enter the model ID manually:
deepseek-v4-proThe model ID must exactly match the model ID in the Yolo Router console.
Save and activate
Click Add or Save to save the Provider.
After saving, activate it so CC Switch writes the configuration to the target CLI config file. If the target CLI is already running, restart it so the new config is loaded.
Test in the target CLI
Run the CLI you configured:
codex "Introduce the model you are using in one sentence"claudeIf the CLI returns a normal response, the integration is working. You can also check the Yolo Router console for the corresponding request log.
Troubleshooting
Fetch Models fails
Check these first:
API Keyis correct and has no extra spacesEndpoint URLmatches the selected App, for example Codex useshttps://api.yolorouter.com/v1- Yolo Router can be reached at
/v1/models
Should the Endpoint URL include /v1?
It depends on the target App. Codex, OpenCode, and OpenClaw usually use https://api.yolorouter.com/v1; Claude Code and Gemini CLI usually use the root endpoint https://api.yolorouter.com.
CLI does not change after activation
Confirm the Provider is saved and activated, then restart the target CLI. Already-running CLI processes usually do not reload config files automatically.
Model not found
Check that the model ID exactly matches the model ID in the Yolo Router console. Do not use a display name, alias, or value with extra spaces.
Trailing slash issues
CC Switch can be sensitive to trailing slashes in Endpoint URLs. Prefer no trailing slash, for example https://api.yolorouter.com/v1, not https://api.yolorouter.com/v1/.