Skip to main content
CC Switch manages local provider configurations for AI command-line tools. Add NexusAPI manually, select that provider in CC Switch, then start the corresponding CLI in a new terminal.

​
Before you start

Prepare an enabled NexusAPI key, the exact model ID available to its group, and the correct endpoint. The API and model capability matrix explains why a model visible on the site may still not fit a given protocol.

​
Install CC Switch

​
macOS

Open CC Switch from Applications after installation.

​
Windows

Download the .msi package from official releases and follow its installer. A portable .zip is also available: extract it, then run the application.

​
Linux

Download the suitable .deb or .AppImage file from official releases. Arch Linux users can use the community-maintained AUR package:
Only download CC Switch from its official repository or its release page. Do not use pages that request payment or NexusAPI credentials.

​
Add a provider

Open Provider management → Add provider, select the target app, enter the fields below, save, switch to the new provider, and restart the CLI. Interface labels can change between CC Switch releases; the endpoint, key, model, and protocol remain the important values. The complete flow is:
Official CC Switch add-provider screen; choose the custom configuration when connecting NexusAPI
Image from the CC Switch official repository, used under its MIT License. The other providers shown are examples only; choose the custom configuration for NexusAPI.
Official CC Switch provider-form example with the key masked
This is an example form from the CC Switch repository. Its URL, model, and gateway name are interface examples only; use the NexusAPI values in the tables below.

​
Claude Code provider

Optional Haiku, Sonnet, and Opus model fields can be left empty, or filled with an available lightweight / Sonnet / Opus model. For a minimal provider, use:
Newer CC Switch releases label the app Claude Code; an older UI can show Claude. Choose the Claude Code provider, not Claude Desktop. Do not append /v1 to the Claude endpoint. After switching providers, open a new terminal and run:
Use /status and then send a short message:

​
Codex provider

For a minimal provider, use:
Codex uses the Responses protocol and therefore requires /v1. The model must be available to the selected key. After switching providers, run:
Make one read-only test request before real work.

​
Confirm the current model list

Use the selected key to see only models it can access:
Copy an ID from data[].id. Choose an anthropic-capable model for Claude Code, and an openai-response-capable model for Codex.

​
Endpoint rules by tool

When in doubt, use this table rather than a value copied from another client.

​
If it does not work

​
It still calls the official address after switching

  1. Confirm that the NexusAPI provider is selected in CC Switch.
  2. Close and reopen the terminal after switching.
  3. Check whether a local configuration of the target CLI overrides the settings written by CC Switch.

​
The API key is invalid

Check that the key was created in NexusAPI Token Management, is enabled, has not expired, has sufficient account credit, and is not blocked by a model restriction. Copy the key exactly; do not add or guess a prefix.

​
The model is unavailable

Check the token group, any model restriction, and the /v1/models output for the same key. If the model is not in that response, do not repeatedly edit CC Switch; use a visible model or contact support with the model name and Request ID.

​
Claude Code asks you to run /login

Do not sign in to an official Claude account for this NexusAPI provider. Switch back to the NexusAPI provider in CC Switch and restart the terminal. Use the provider configuration, not Claude Code’s official login, for the gateway key.
  1. Add the provider manually in CC Switch.
  2. Use /v1/models with the selected key to identify usable models.
  3. Verify with a short request before a complex task.