Getting Started
Prerequisites
Section titled “Prerequisites”You need two things:
- Claude Code installed globally
- A JavaScript runtime, Bun 1+, Node.js 18+, or Deno 1+
If you don’t have Claude Code yet:
npm install -g @anthropic-ai/claude-codeInstall claude-multi
Section titled “Install claude-multi”Pick whichever package manager you already use:
# Bunbun add -g claude-multi
# npmnpm install -g claude-multi
# pnpmpnpm add -g claude-multi
# Denodeno install -g npm:claude-multiThe entry point is a polyglot file that auto-detects your runtime, you don’t need to configure anything.
Create your first instance
Section titled “Create your first instance”Launch the interactive TUI:
claude-multiSelect Add new instance and follow the wizard:
- Instance name, something short like
glmordeepseek. This becomes your command (claude-glm,claude-deepseek). - Provider template, pick from the list, or choose
None / Customfor manual setup. - API key, paste your key (masked input, stored in the instance’s
settings.json). - Confirm paths, accept the defaults (
~/.claude-<name>/for config,~/.local/bin/claude-<name>for the binary). - Copy options, optionally copy settings, plugins, or everything from your default
~/.claude. - Auto-sync, if you copied all files, choose whether to symlink plugins/skills back to
~/.claude.
When the wizard finishes:
✓ Instance 'deepseek' created successfully! ├─ Binary: /Users/you/.local/bin/claude-deepseek └─ Config: /Users/you/.claude-deepseekRun it:
claude-deepseekThat’s a full Claude Code session connected to DeepSeek, with its own isolated config. Same claude binary you already know, pointed at a different provider.
CLI quick start
Section titled “CLI quick start”You can also create instances directly from the command line without the TUI:
claude-multi add deepseek --provider deepseek --api-key sk-your-keyclaude-multi add glm --provider glm --api-key your-zai-keyThen run them:
claude-deepseekclaude-glmAdd ~/.local/bin to your PATH
Section titled “Add ~/.local/bin to your PATH”If claude-<name> isn’t found after creation, your global binary directory probably isn’t on PATH. Add it once:
# zsh (macOS default)echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrcsource ~/.zshrc
# bashecho 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrcsource ~/.bashrcThe exact binary location depends on your package manager, the TUI will show the actual path when the instance is created.
What’s next
Section titled “What’s next”- Providers: full list of provider templates and model mappings
- Usage: all CLI commands and flags
- Configuration: settings file reference
- Plugins & MCP: manage plugins and MCP servers across instances