DEV Community: dougame

How to Use CC Switch to Manage Multiple AI API Configurations (2026 Guide)

dougame — Mon, 21 Sep 2026 03:12:29 +0000

If you use multiple AI coding tools (Claude Code, Cursor, Cline, Codex) or switch between different API providers, you've probably dealt with the headache of managing multiple configurations:

Editing config files every time you switch providers
Remembering which base URL goes with which key
Copy-pasting environment variables between terminals
Forgetting which model you last configured

CC Switch solves all of this. It's a lightweight desktop app that lets you save multiple API configurations and switch between them with one click.

This guide walks through how to set it up and use it effectively.

What is CC Switch?

CC Switch is a configuration manager specifically for AI coding tools. Think of it as a "profile switcher" for your API settings.

Instead of manually editing config files every time you want to switch:

From work API to personal API
From one model provider to another
From Claude Code to Cursor

You just open CC Switch, click a profile, and it updates all the config files for you.

Supported tools

CC Switch currently supports:

Claude Code (Anthropic CLI)
Cursor (AI code editor)
Cline (VS Code extension)
Codex (OpenAI CLI)
And more being added

When you switch a profile, it updates the settings for all supported tools at once.

Installation

CC Switch is available for macOS, Windows, and Linux.

Go to the GitHub releases page
Download the installer for your OS
Install and open the app

It's a lightweight native app - no Electron bloat, starts instantly.

Adding your first configuration

When you first open CC Switch, you'll see an empty configuration list. Let's add one.

Step 1: Click "Add Configuration"

You'll see a form with fields for:

Name: A label for this configuration (e.g., "Work Claude", "Personal DeepSeek")
Provider: Which tool this is for (Claude Code, Cursor, etc.)
Base URL: The API endpoint URL
API Key: Your API key
Model: The default model to use

Step 2: Fill in the details

For example, if you're using JZS Token (https://jzstoken.com) as your API provider:

Name: "JZS Token - Claude Sonnet"
Provider: Claude Code
Base URL: https://jzstoken.com/api/v1
API Key: your JZS Token API key
Model: claude-sonnet-5

Step 3: Save

Click save. Now you have your first configuration.

Adding multiple configurations

The real power of CC Switch is when you have multiple configurations for different use cases.

Here's what our setup looks like:

Name	Tool	Model	Use case
JZS - Flash	Claude Code	deepseek-v4-flash	Routine refactoring, simple questions
JZS - Mid	Claude Code	deepseek-v4-pro	Standard coding tasks
JZS - Frontier	Claude Code	claude-sonnet-5	Hard reasoning, architecture
JZS - Cursor	Cursor	qwen-3.6-flash	Autocomplete
Work - Official	Claude Code	claude-sonnet-5	Work projects (using official Anthropic key)

Now switching between them is just one click.

Switching configurations

To switch:

Open CC Switch
Click the configuration you want to use
Click "Apply"

That's it. CC Switch updates the config files for all supported tools automatically. No need to manually edit anything.

The next time you open Claude Code or Cursor, it's using the new configuration.

Why this is better than editing configs manually

Before CC Switch:

# Switch to flash model
export ANTHROPIC_BASE_URL="https://jzstoken.com/api/v1"
export ANTHROPIC_API_KEY="sk-xxx"
export ANTHROPIC_MODEL="deepseek-v4-flash"

# Switch to frontier model
export ANTHROPIC_MODEL="claude-sonnet-5"

After CC Switch:

Open app
Click "JZS - Frontier"
Done

No typos, no forgotten env vars, no "wait why is it using the wrong model?" debugging.

Setting up with JZS Token

If you haven't set up your API provider yet, here's how to get started with JZS Token:

Go to https://jzstoken.com
Sign up and get an API key
The base URL is: https://jzstoken.com/api/v1
It supports 40+ models (DeepSeek, Qwen, Kimi, GLM, Claude, GPT, Grok, Doubao, etc.)
It supports all three protocols: Chat Completions, Responses, and Messages

This means the same API key works for:

Claude Code (Messages protocol)
Cursor (OpenAI compatible)
Cline (OpenAI compatible)
Codex (OpenAI compatible)

You can create multiple CC Switch configurations all pointing to the same JZS Token key, just with different default models. That's the sweet spot - one key, multiple model profiles, switchable with one click.

Pro tips

Name your configurations clearly. Don't just name them "Config 1" and "Config 2". Use descriptive names like "Flash - Routine Work" or "Frontier - Architecture".
Use model tiering. The biggest cost savings come from using cheaper models for routine tasks. Have at least 2-3 configurations at different price points.
Keep work and personal separate. If you use different API keys for work and personal projects, CC Switch makes it trivial to switch between them without mixing up keys.
Test before you rely on it. When you add a new configuration, open your AI coding tool and send a test request to make sure it's working before you start a big project.

Wrapping up

CC Switch is one of those tools that seems small until you start using it, and then you wonder how you lived without it. Once you have more than 2 API configurations, the manual switching process becomes a real time sink.

Combined with a good multi-model API gateway like JZS Token, it's the most flexible setup we've found:

One API key for all models
Multiple configurations for different tasks
One-click switching between them

Give it a try if you're juggling multiple AI coding tools or providers. You'll save more time than you think.

Have you tried CC Switch? What's your setup? Let me know in the comments.

How to Configure Third-Party APIs for AI Coding Agents (Claude Code, Cursor, Cline, Codex)

dougame — Mon, 21 Sep 2026 03:10:52 +0000

If you're using AI coding tools like Claude Code, Cursor, Cline, or Codex, you've probably wondered: can I use a different API provider than the default? The answer is yes - almost all of these tools support custom API endpoints.

This guide covers how to configure third-party APIs for the most popular AI coding agents, plus a tool that makes switching between configurations much easier.

Why configure a third-party API?

Before we get into the how, let's talk about why you'd want to do this in the first place:

Cost savings: Frontier models are expensive. Routine coding tasks don't need the most expensive model.
More model choice: Maybe you want to use DeepSeek, Qwen, Kimi, or GLM instead of only Claude or GPT.
No vendor lock-in: Don't want to be tied to one provider's pricing or TOS.
Better performance: Some providers are faster or cheaper for specific tasks.

The common pattern

Almost all modern AI coding tools follow the same pattern: they speak the OpenAI-compatible API format. That means you just need three things:

A Base URL for the API endpoint
An API Key for authentication
A model name to specify which model to use

Let's go through each tool.

Claude Code

Claude Code uses Anthropic's Messages API format. To configure a custom endpoint:

# Set environment variables
export ANTHROPIC_BASE_URL="https://your-api-endpoint.com"
export ANTHROPIC_API_KEY="your-api-key"

Or in your Claude Code settings file, set:

ANTHROPIC_BASE_URL
ANTHROPIC_AUTH_TOKEN

Note: Claude Code uses the Messages protocol (/v1/messages), not Chat Completions. Make sure your API provider supports the Messages format.

Cursor

Cursor supports custom OpenAI-compatible endpoints out of the box:

Open Cursor Settings
Go to Models
Click Add Model
Select OpenAI API as the provider
Enter:
- Base URL: your API endpoint (e.g., https://your-api.com/v1)
- API Key: your key
- Model Name: the model you want to use

That's it. Now you can select this model from the dropdown in the chat.

Cline (VS Code extension)

Cline also supports custom OpenAI-compatible providers:

Open Cline settings
Go to API Configuration
Select OpenAI Compatible as the API Provider
Enter:
- Base URL: your endpoint URL
- API Key: your key
- Model ID: the model name

Cline is very flexible - you can add multiple providers and switch between them.

Codex (OpenAI's CLI)

OpenAI's Codex CLI also supports custom endpoints:

# Set environment variables
export OPENAI_BASE_URL="https://your-api-endpoint.com/v1"
export OPENAI_API_KEY="your-api-key"

Or in your config.toml, set the provider settings.

Zed Editor

Zed has built-in support for custom model providers:

Open Zed Settings
Go to Assistant
Under Model Providers, click Add Provider
Select OpenAI Compatible
Enter the Base URL and API key

Switching between configurations: CC Switch

Once you have multiple API configurations (e.g., one for work, one for personal, one for testing different models), managing them all gets tedious. That's where CC Switch comes in.

CC Switch is a simple tool that lets you:

Save multiple API configurations (different endpoints, keys, models)
Switch between them with one click
No need to manually edit config files or environment variables every time

It supports Claude Code, Cursor, and other tools. If you're juggling multiple API providers, it saves a lot of context switching.

Which API provider to use?

You need an API provider that:

Is OpenAI-compatible (or supports the Messages protocol for Claude Code)
Has the models you want
Has transparent pricing
Doesn't require a monthly subscription

I've been using JZS Token (https://jzstoken.com) as my API gateway. It's a single OpenAI-compatible endpoint at https://jzstoken.com/api/v1 that gives you access to 40+ models: DeepSeek, Qwen, Kimi, GLM, Claude, GPT, Grok, Doubao, and more.

Why I like it:

One key, all models: No more juggling 10 different API keys
All three protocols: Chat Completions, Responses, and Messages
Pay as you go: Credits don't expire, no monthly commitment
Transparent pricing: All rates listed upfront, no surprise bills

The setup for any tool is the same:

Base URL: https://jzstoken.com/api/v1
API Key: your JZS Token key
Model: whatever model you want to use

Putting it all together

Get an API key from a provider like JZS Token
Configure your AI coding tool with the Base URL and key
Use CC Switch to manage multiple configurations if you have more than one

The whole setup takes 5 minutes, and then you can use whatever model makes the most sense for each task - instead of being locked into one provider's pricing.

Have you configured custom APIs for your AI coding tools yet? What's your setup? Let me know in the comments.