A separate Claude Code
for each provider.
Each provider gets its own claude-<name> command and config directory. That command runs the normal claude binary, and your existing ~/.claude stays untouched.
{
"env": {
"ANTHROPIC_BASE_URL": "https://api.z.ai/api/anthropic",
"ANTHROPIC_MODEL": "glm-5.3[1m]",
"ANTHROPIC_DEFAULT_OPUS_MODEL": "glm-5.3[1m]",
"ANTHROPIC_DEFAULT_SONNET_MODEL": "glm-5.3[1m]",
"ANTHROPIC_DEFAULT_FABLE_MODEL": "glm-5.3[1m]",
"ANTHROPIC_DEFAULT_HAIKU_MODEL": "glm-5.3-flash[1m]",
"CLAUDE_CODE_EFFORT_LEVEL": "high",
"CLAUDE_CODE_ALWAYS_ENABLE_EFFORT": "1"
}
}Why it exists
Why a second provider breaks your setup.
Claude Code keeps one config directory: ~/.claude. It holds settings, MCP servers, plugins, skills, and conversation history. That works while you use one provider. Add a second and the same files have to serve both setups. Change the base URL for GLM and your Anthropic sessions follow it. Swap in a DeepSeek key and the old key is gone. Copy the directory by hand and you are maintaining two setups that drift.
claude-multi is a free, MIT-licensed CLI for people who switch providers during the day. It ships eight templates for six providers: GLM, MiniMax, DeepSeek, MiMo, Kimi, and Qwen. You might keep Claude on your main account, use GLM for a long refactor, and send cheap batch work to DeepSeek. Or you might test a model before moving a team onto it. The goal is to change models without rebuilding the setup around them.
Isolation is literal. claude-multi add glm creates~/.claude-glm/ with its own settings.json, credentials, sessions, and history. The claude-glm wrapper setsCLAUDE_CONFIG_DIR to that directory, then runs the officialclaude binary. Your normal ~/.claude setup is left as it is. Plugins and skills can be symlinked from your primary install, so you install them once. MCP servers remain entries in the instance'ssettings.json. The central registry at~/.claude-multi/ tracks instances, health, and backups. It does not store each instance's settings.
Install with npm install -g claude-multi, or use bun or pnpm. Run claude-multi for the menu, orclaude-multi add glm to create an instance and paste a key. Thesetup guide covers the rest, theprovider pages list endpoints and model mappings, theblog has notes on model choice, and theFAQ answers common questions.
Install
Install with npm, bun, or pnpm. Then add a provider.
Run claude-multi to open the menu, orclaude-multi add glm to create an instance and paste a key. The getting started guidewalks through the prompts.
- Node 22+ or Bun 1+
- macOS, Linux, Windows
bun add -g claude-multinpm install -g claude-multipnpm add -g claude-multiOne config directory per instance.
Each instance keeps its settings, credentials, and history in~/.claude-<name>. Your existing~/.claude is not modified.
Six providers, eight templates.
Each template sets the base URL and model names for one provider or plan. Pick one, paste a key, and the config lands in~/.claude-<name>/settings.json. Your existing ~/.claude is not touched.
Counts include the MiMo Token Plan and Qwen Coding Plan. Anthropic is not a template: your existing ~/.claudesetup stays as it is. Templates pin the models listed above. Check a provider page for exact model IDs, plan coverage, regional endpoints, and current pricing.