> ## Content Index > Fetch the complete content index at: https://orbiorbi.com/news/llms.txt > Use this file to discover other available public pages before exploring further. # CC Switch aggregation: configure and use multiple providers - URL: https://orbiorbi.com/news/en/cc-switch-aggregation-setup-guide/ - Published: 2026-10-21T20:54:40.000Z - Updated: 2026-10-21T20:54:40.000Z - Description: CC Switch 4.0 adds aggregation, placing models from multiple providers in one client selector. Learn to back up and update, add models, switch in the client and recover direct connections, including default-provider and restart rules. - Author: Orbis News - Tags: API integration and troubleshooting, #en, #mt-review ## 1\. See the goal before starting **The goal: put two working providers in one client, complete a request with each and restore direct mode afterward.** CC Switch 4.0 introduces aggregation mode. Choose a model in Claude Code or Codex and the request goes to its provider, without returning to CC Switch every time you switch. ![The Codex model selector listing models from different providers](https://orbiorbi.com/news/content/images/2026/10/02-codex-model-picker.png) *Look at the provider after each model name. Available models depend on the providers you have configured.* | Mode | Suitable for | Remember | | ----------- | ----------------------------------------------------- | -------------------------------------------------------------- | | Direct | Using one provider daily | The client connects directly to the provider | | Routing | Protocol conversion and failover | A local forwarding service must run | | Aggregation | Choosing multiple providers' models inside the client | Requests follow your selection; there is no automatic failover | This guide was checked on October 22, 2026, when the latest stable release was v4.0.18\. Aggregation supports only Claude Code and Codex; configure each app separately. ## 2\. Install or update ### 1\. Back up before updating - Wait for running tasks to finish. - Open Settings → Data, export an SQL backup and preserve the client's original settings. - Check for updates under Settings → About. New users can download an installer from the [official page](https://ccswitch.io/download?ref=orbiorbi.com). On Windows, choose an MSI matching your architecture. On a Mac, open the DMG and drag the app to Applications. **Success check:** the new version opens and the original providers are still there. Version 4.0 changes the database structure. Automatic pre-upgrade backups are in `.cc-switch/backups/`. Older software may not read the new database; a downgrade needs a matching backup, not just an older installer. ### 2\. Optional: ask an agent to install it > Follow the official instructions at https://github.com/farion1231/cc-switch to check my system, back up existing settings and install or update to the latest stable release. Preserve sign-in and custom settings, and do not enable aggregation automatically. Report the version, backup location and whether the client meets the requirements. This needs an agent with local execution capabilities. You may still need to complete browser sign-in and system authorization yourself. ### 3\. Check clients and accounts - Check client versions in the CC Switch Apps page. - Claude Code must be ≥2.1.243\. Check with `claude --version` in a terminal; a native installation can be updated with `claude update`. - Sign in to official accounts in the respective clients first. In Claude Code, run `claude` and follow the prompts. In Codex, run `codex` and select **Sign in with ChatGPT** to authorize. - Use `/status` to check the current configuration and send a short message to confirm the official route works. Verify API routes separately too. - Understand the account restrictions below, then connect Orbis as one of the API services. ![Application management showing current tool versions and update buttons](https://orbiorbi.com/news/content/images/2026/10/apps-zh.png) *Check only the tools you intend to use. The versions in the screenshot reflect when it was captured.* | Account situation | Can you complete this exercise? | | ------------------------------------------ | ----------------------------------------------------------- | | Only an official Claude subscription | Aggregation is not currently supported; stay in direct mode | | Official Codex account plus an API service | The official account must be the default | | Two supported API services | Configure and verify each before adding them | **Success check:** client versions meet the requirements and you have working access to both services. ## 3\. Configure aggregation ### 4\. Connect Orbis, then choose models for each provider - Sign in to [Orbis](https://orbiorbi.com/?ref=orbiorbi.com), open the appropriate model page below, choose a route and obtain a key. - In route details, open Quick integration → select a key → Tool integration → Codex CLI or Claude Code → Fill in CC Switch. Check the import before confirming. - **Keys are bound to routes**; changing only the model ID does not switch routes. Import links contain keys and should not be shared. See the [Orbis quick start](https://orbiorbi.com/docs/quickstart/?ref=orbiorbi.com) for the full entry point. | Client | Model and route | Custom configuration details | | ----------- | --------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | Codex | [GPT 6.1 Sol](https://orbiorbi.com/pricing/gpt-6.1-sol?catalogKey=model%2F91&ref=orbiorbi.com), GPT · HA | Endpoint https://api.orbiorbi.com/v1; OpenAI Responses; model gpt-6.1-sol | | Claude Code | [Claude Haiku 5.5](https://orbiorbi.com/pricing/claude-haiku-5-5?catalogKey=model%2F112&ref=orbiorbi.com), Claude Code · AH | Endpoint https://api.orbiorbi.com; Anthropic Messages; model claude-haiku-5-5 | Model [GPT 6.1 Sol](https://orbiorbi.com/pricing/gpt-6.1-sol?catalogKey=model%2F91&ref=news-cc-switch-aggregation-setup-guide)`gpt-6.1-sol` View the model used in this guide and integration details for its available routes. Try it If automatic import is unavailable, select the client on the left → Add provider → Custom configuration, then enter the table's values. For Codex, enter the key in the editor's `OPENAI_API_KEY` field and keep `wire_api` as `responses`. For Claude, use `ANTHROPIC_AUTH_TOKEN`, set `ANTHROPIC_BASE_URL` to the endpoint, and set both `ANTHROPIC_MODEL` and `ANTHROPIC_DEFAULT_HAIKU_MODEL` to `claude-haiku-5-5` so that the main and background models remain within the route's authorized range. Keep Full URL off and do not append request paths yourself. An Orbis card is configuration you add; do not assume the app has a built-in preset. Model [Claude Haiku 5.5](https://orbiorbi.com/pricing/claude-haiku-5-5?catalogKey=model%2F112&ref=news-cc-switch-aggregation-setup-guide)`claude-haiku-5-5` View the model used in this guide and integration details for its available routes. Try it Then open Aggregation at the top of this client's page. **Selecting the tab only opens the page.** Edit the Orbis card's Model list: - Select Fetch model list, search for models supported by the current route, select them and choose Add selected models. - If the route has no list endpoint, select Add manually and enter the actual model ID from the table. Choose a recognizable display name. - Configure the second provider's endpoint, key and model according to its documentation. Start with one model per provider. **Success check:** both cards have the correct model. Two Orbis models still belong to one service; if Orbis is your only service, you can practice model switching but have not yet completed the two-provider goal. Autocomplete fills missing parameters without overwriting existing values. Entering a larger context window does not increase the model's real capabilities. ### 5\. Add providers, set a default and enable aggregation - Select Add on a card in the Available area. - Select Switch to aggregation mode. - In the confirmation dialog, check the default provider and model count, then confirm. ![The aggregation page showing its default provider, added providers and restart notice](https://orbiorbi.com/news/content/images/2026/10/01-cc-switch-aggregation.png) *Check Aggregation active at the top, the default card and the added count, in that order. Brands and balances shown in the example are not recommendations.* The default provider handles ordinary requests that do not explicitly name an aggregation route. In Codex, OpenAI Official can only be the default; it cannot be added as an ordinary member. **Success check:** the header shows Aggregation active. Saving a provider, adding it to the list and enabling aggregation are three different steps; complete all three. ## 4\. First use: verify two requests ### 6\. Make the client reload its model list | Client | After changing the list or model settings | | ---------------------- | -------------------------------------------------------------------- | | Codex desktop | Fully quit and reopen; on a Mac, use Command+Q | | Codex CLI | Restart the daemon when prompted, then reopen the CLI | | Codex editor extension | Reopen the editor window | | Claude Code | The list usually updates immediately; reselect the model if prompted | The daemon is a shared background program; restarting it may interrupt other tasks. Switching models within an already loaded list does not require restarting every time. **Success check:** the client shows the models just added, rather than only the old list. ### 7\. Choose the first provider, then the second - Choose the first provider and send: > Explain the difference between backup and synchronization in five sentences. Only answer; do not operate on files. - After receiving the answer, switch to the second provider in the same conversation and send: > Check the explanation above and identify two points that beginners might misunderstand. Only answer. Claude Code users can enter `/model` to open the selector: ![The Claude Code model list identifying model names and providers](https://orbiorbi.com/news/content/images/2026/10/03-claude-code-model-picker.png) *Select an entry using its provider label. You do not need to invent a ccs- prefix yourself.* **Success check:** both providers answer and their routes can be checked against request records. ## 5\. Advanced use and recovery ### 8\. Switch according to the stage of a task - Discuss a plan with a familiar model, then switch to another to check for omissions. - Before switching, confirm that the conversation history is appropriate to send to the next provider. - Avoid frequent changes in a long conversation. A new model may rebuild its cache, increasing the first round's cost. **Success check:** you know why you are switching and have confirmed that the next provider supports the task's image or tool requirements. Keep CC Switch running during aggregation. After learning the basic workflow, configure subagent roles; retain the cross-provider compatibility setting first and avoid changing several advanced options at once. ### 9\. Add models to the same provider - Edit the provider, fetch its Model list again and select additional models. - If fetching fails, choose Add manually and enter the actual model ID supported by the service. - Keep display names recognizable and check the default model. After saving, refresh the client as described in step 6. One Orbis card can contain several models, but they still come from one API service. This is not redundancy across providers. Different model developers do not necessarily mean different access routes either. **Success check:** both old and new models appear in the selector and request records still belong to the correct provider. Autocomplete fills only missing information; actual capabilities depend on the service. ### 10\. Use another model for Codex subagents - Open the gear in the top-right of the aggregation page → Aggregation settings. - Under Subagent model, choose a model already published to the aggregation list. Leave reasoning effort at Model default initially. - Across providers, keep Use classic tools for subagents in aggregation mode enabled and start a new conversation before using it. This is the default model for subtasks; if the main agent explicitly chooses one, the task setting takes precedence. To undo it, choose Follow main model. Task content goes to the respective service when crossing providers, so confirm that the data is appropriate to share first. **Success check:** subtasks in a new conversation use the selected configuration. If a task cannot be decrypted, check the classic-tools switch and restart Codex when prompted rather than only changing the API key. ### 11\. Recover direct mode first when something fails - Select Back to direct and choose a provider that previously worked. - Restart the client when prompted and send a short request. - Before removing the current default, make another provider the default. ![The main screen in direct mode with a provider marked In use](https://orbiorbi.com/news/content/images/2026/10/main-zh.png) *This is a Claude Code direct-mode example. Codex users should remain on the Codex page and check the same mode and current-provider status.* **Success check:** a direct request answers again. Exiting CC Switch normally restores direct mode; after a forced termination, reopen the app and check its state. | Problem | Check first | | ------------------------------------- | -------------------------------------------------------------------------- | | Cards are listed but no models appear | Whether Model list is populated and the provider has been added | | Codex still shows the old list | Full reload and, for the CLI, daemon restart | | One service fails | Key, model ID, permissions and allowance; manually choose another provider | | Errors continue after removal | Reselect an existing model rather than using an old entry | If the cause is still unclear, open Settings → Data → Application diagnostic logs and look up the failure time. If the header reports an environment-variable conflict, check whether an old endpoint overrides the new settings; do not clear every variable. Conceal keys and request content before exporting logs. Before importing pre-upgrade SQL, back up the current database. Importing replaces provider, MCP, prompt, usage and other records as a whole. Complete one request per provider and restore direct mode before gradually adding more providers. ## References and images Operations follow the [official aggregation manual](https://github.com/farion1231/cc-switch/blob/main/docs/user-manual/zh/4-proxy/4.6-aggregation.md?ref=orbiorbi.com) and [official illustrated guide](https://github.com/farion1231/cc-switch/blob/main/docs/guides/aggregation-mode-guide-zh.md?ref=orbiorbi.com). Structural references include [QCode](https://qcode.cc/cc-switch-4-aggregate-mode?ref=orbiorbi.com), [Gunzo](https://gunzo.cc/content/how-to-use-cc-switch?ref=orbiorbi.com) and [XieCoding](https://xiecoding.cn/view/855.html?ref=orbiorbi.com); outdated facts were not carried over. Images are originals from the official documentation, licensed under MIT, Copyright (c) 2025 Jason Young. Brands belong to their respective owners.