Manage everything from one interface: Codex, Claude, and Gemini.
CC Switch is an open-source, cross-platform configuration manager for AI coding tools. Its visual interface lets you manage providers, Base URLs, API keys, and protocol settings without repeatedly editing configuration files by hand.
Why do we recommend CC Switch?
When you use several AI coding clients, CC Switch brings scattered settings together in one visual interface.
Replace manual file editing with select-and-enable.
Codex, Claude Code, and Gemini CLI use different configuration locations, field names, and API conventions. CC Switch manages these differences, making provider switching and configuration maintenance much easier.
Choose the package for your operating system.
Available package types may change between releases. Always use the latest assets shown on the GitHub Releases page.
Windows
On Windows 10 or later, choose either the installer or portable package.
macOS
Download a DMG from Releases or install with Homebrew.
Linux
Choose AppImage, DEB, RPM, or the appropriate community package for your distribution.
First, choose the client you want to configure.
Different applications may use different protocols and Base URLs. Do not apply an identical configuration to Codex, Claude Code, and Gemini CLI.
Codex Configuration
Use this setup for Codex CLI or the Codex app. Start with OmniDino’s OpenAI-compatible endpoint, then choose Responses or compatibility mode based on the model’s required endpoint.
Claude Code Configuration
Claude Code normally uses the root URL because the client or CC Switch generates the specific Claude request path. Do not append OpenAI’s /v1 to the root URL.
Gemini CLI Configuration
First confirm the Gemini route and protocol currently provided by OmniDino, then enter them in the Gemini CLI profile. The model name must exactly match the name shown in the dashboard.
Other Compatible Tools
Tools such as OpenCode, OpenClaw, and Hermes may use OpenAI Chat Completions or other protocols. Select the correct application first, then complete the fields required by that application.
/v1.From OmniDino to an active client configuration.
The steps below describe the general process. Use the application-specific configuration cards above for exact field values.
Prepare Your Account, Balance, and API Key
Sign in to the OmniDino dashboard, confirm that your balance is available, and create a dedicated API key for CC Switch or the target client.
Install and Open CC Switch
Download the correct package from the official GitHub Releases page, install it, and open the application.
Select the Target Application First
Choose Codex, Claude Code, Gemini CLI, OpenCode, or the actual target application from the application selector. The application type determines the configuration file and protocol behavior.
Add OmniDino as a Provider
Click Add Provider or “+”, choose a custom configuration, and enter OmniDino as the provider name.
Enter the URL, Key, Protocol, and Model
Enter the Base URL required by the target application. Codex and OpenAI-compatible tools usually use a URL ending in /v1, while Claude Code normally uses the root URL.
Save and Set as the Active Configuration
Saving a profile does not always activate it. Confirm that the provider card is marked as enabled or current.
Restart the Target Client and Test
Completely close the existing terminal or client window, reopen it, and send a simple request. Then check the OmniDino dashboard for a corresponding usage record.
Configuration fields that are commonly entered incorrectly.
| Field | OmniDino Recommendation | Notes |
|---|---|---|
| Provider Name | OmniDino |
This is only a local display name. Add a suffix such as Codex or Claude to distinguish profiles. |
| Codex Base URL | https://api.omnidino.com/v1 |
Used for OpenAI-compatible clients or OmniDino’s Codex route. |
| Claude Base URL | https://api.omnidino.com |
Claude Code normally uses the root URL to avoid duplicating request paths. |
| API Key | A dedicated key created in the dashboard | Do not expose a complete key in screenshots or commit it to a public repository. |
| Wire API | Choose Responses, Claude, or a compatible protocol based on the application | An incorrect protocol may cause 404 errors, request-conversion failures, or unexpected response formats. |
| Model | The exact name shown in the model catalog | Preserve capitalization, hyphens, and version suffixes. Do not guess model names. |
Which tools can CC Switch manage?
Supported applications may evolve between versions. The tools below are the primary ones covered by this guide.
Check these items first when configuration fails.
Still having trouble configuring OmniDino?
When contacting support, include your operating system, CC Switch version, target client, model name, Base URL, and complete error message. Hide your API key.
[email protected]