bbed2a1fe1
Reorganize docs/user-manual/ from flat structure to language subdirectories (zh/, en/, ja/) with shared assets/. Move existing Chinese docs into zh/, fix image paths, add multilingual navigation README, and translate all 23 markdown files (~4500 lines each) to English and Japanese.
2.5 KiB
2.2 Switch Provider
Switch from Main Interface
In the provider list, click the "Enable" button on the target provider card.
Switching Flow
- Click the "Enable" button
- CC Switch updates the configuration file
- The card status changes to "Currently Active"
- Claude/Gemini take effect immediately, Codex requires a terminal restart
Status Indicators
| Status | Display | Description |
|---|---|---|
| Currently Active | Blue border + label | Current provider in the configuration file |
| Proxy Active | Green border | Provider actually in use during proxy mode |
| Normal | Default style | Inactive provider |
Quick Switch via System Tray
Quickly switch providers via the system tray without opening the main interface.
Steps
- Right-click the CC Switch icon in the system tray
- Find the corresponding app (Claude/Codex/Gemini/OpenCode) in the menu
- Click the provider name you want to switch to
- Switching completes with a brief tray notification
Tray Menu Structure
Activation Methods
Claude Code
Takes effect immediately after switching, no restart needed.
Claude Code supports hot reload and automatically detects configuration file changes and reloads.
Codex
Requires restart after switching:
- Close the current terminal window
- Reopen the terminal
Gemini CLI
Takes effect immediately after switching, no restart needed.
Gemini CLI re-reads the .env file on each request.
Configuration File Changes
When switching providers, CC Switch modifies the following files:
Claude
~/.claude/settings.json
Modified content:
{
"env": {
"ANTHROPIC_API_KEY": "new API Key",
"ANTHROPIC_BASE_URL": "new endpoint"
}
}
Codex
~/.codex/auth.json
~/.codex/config.toml (if additional configuration exists)
Gemini
~/.gemini/.env
~/.gemini/settings.json
Handling Switch Failures
If switching fails, possible reasons:
Configuration File Is Locked
Another program is using the configuration file.
Solution: Close the running CLI tool and try switching again.
Insufficient Permissions
No write permission to the configuration file.
Solution: Check the permission settings of the configuration directory.
Invalid Configuration Format
The provider's JSON configuration has format errors.
Solution: Edit the provider, check and fix the JSON format.