Skip to main content
CC Switch is a cross-platform desktop app for adding, enabling, and switching Providers for tools such as Claude Code, Codex, Gemini CLI, OpenCode, OpenClaw, and Hermes. This guide follows the CC Switch quickstart flow and adds the Nusabase Endpoint values each tool should use.
Different tools use different protocols, so their Nusabase Endpoints are different. Claude Code’s Anthropic Messages setup uses the root URL https://api.nusabase.io; OpenAI-compatible setups use https://api.nusabase.io/v1. If you use CC Switch’s Universal Provider, only select tools that share the same Endpoint type. When configuring Claude Code together with OpenAI-compatible tools, add separate Providers per tool.

When To Use This

  • You want to manage Nusabase API keys and model settings in CC Switch.
  • You use multiple AI coding tools such as Claude Code, Codex, OpenCode, OpenClaw, and Hermes.
  • You prefer switching Providers in a graphical interface instead of editing JSON/TOML files by hand.
  • You want CC Switch to fetch the Nusabase model list for you.

Prerequisites

  • CC Switch is installed.
  • The target CLI tools are installed and have been launched at least once so they create their default config directories.
  • You have a Nusabase API key: sk-....
  • Your machine can reach https://api.nusabase.io.
  • The example model qwen3.5-flash is only for demonstration; use /v1/models as the source of truth for your account.

Install CC Switch

After installing, open CC Switch. On the left side of the interface, select Tools, and on the right side, manage the Provider for this tool. Click the + in the top right corner to add a new Provider.

Verify Nusabase First

Before configuring CC Switch, confirm that your API key and model access work.

Quick Setup Flow

  1. At the top of the CC Switch interface, choose the tool you want to configure, like Claude Code, Codex, or OpenCode.
  2. Click the + button in the top-right corner.
  3. Choose the right preset: Custom is typical for Claude Code; OpenAI Compatible or Custom is typical for OpenAI-compatible tools.
  4. Fill in the Provider name, API key, Endpoint URL, and model.
  5. If available, click the Fetch Models button next to the model field to pull models from Nusabase /v1/models.
  6. Click Add.
  7. Click Enable on the Provider card.
  8. Restart the terminal or reopen the CLI as required by the tool, then send a test message.
When adding a Provider, focus on API Key and Request URL. Choose the request URL from the table below. CC Switch add provider screen

Nusabase Settings Table

Common fields:
Do not paste a full endpoint path such as https://api.nusabase.io/v1/chat/completions into Endpoint URL. CC Switch and the target tool append the protocol-specific path.

Claude Code Notes

Claude Code appends /v1/messages to ANTHROPIC_BASE_URL, so the Endpoint URL must be the root URL:
Recommended settings: If you manually edit ~/.claude/settings.json, the usual shape is:
You can also use ANTHROPIC_AUTH_TOKEN if you want Claude Code to send authentication as Authorization: Bearer.

Codex Notes

Codex clients call the OpenAI Responses API. When connecting Codex to Nusabase through CC Switch, enable CC Switch local routing and set the Provider’s upstream format to Chat Completions. CC Switch will convert Codex /responses requests into Nusabase OpenAI-compatible Chat Completions requests. Set Endpoint URL to:
Recommended settings:
Do not use /v1/responses as the direct upstream format for the CC Switch Codex Provider. Direct Responses routing may fail with unexpected status 503 Service Unavailable: CC Switch local proxy failed while handling Codex endpoint /responses ... upstream_status: HTTP 503; cause: DistributorGetChannelFailed. Enable local routing and set the upstream format to chat/completions instead.

Codex Local Routing

Local routing is recommended for Codex with Nusabase. It is useful when:
  • You want CC Switch to convert Codex /responses requests into Nusabase’s more stable /chat/completions path.
  • You want all Codex requests to pass through CC Switch and appear in its routing logs.
  • You are debugging Provider switching or request forwarding and need to observe the proxy path.
Setup:
  1. Open CC Switch Settings → Advanced → Routing Service.
  2. Start the routing service. The default listener is 127.0.0.1:15721.
  3. In App Routing, enable the Codex routing toggle. CC Switch Configure application routing
  4. In the Codex Nusabase Provider advanced options, set the Upstream Format to “Chat Completions”. CC Switch Select upstream format
  5. Keep Endpoint URL as https://api.nusabase.io/v1.
When converted to Chat Completions, the path is:

OpenCode / OpenClaw / Hermes Notes

When these tools use OpenAI-compatible Chat Completions, set Endpoint URL to:
Common settings: After configuration, close and reopen the terminal, then start the target tool.

Fetch Models

CC Switch can fetch models from the Provider’s model endpoint. After filling in API Key and Endpoint URL, click the Fetch Models button next to the model field. Common failures:

Apply And Verify

Provider switching behavior varies by tool: Success criteria:
  • The Nusabase Provider is enabled in CC Switch.
  • The tool’s model picker or /model command shows the Nusabase model.
  • A test message returns normally.
  • If you use Codex local routing, CC Switch’s routing panel shows proxied request logs.

Troubleshooting

See Models and Pricing for current models, context windows, and pricing.

References