Every open model, no env block to swap
AutoRouter puts Kimi, DeepSeek, GLM and MiniMax in the Claude Code and Codex pickers beside Claude and GPT, with no keys or base URLs, and picks one for each turn. One prompt to your coding agent switches you over, model settings included.
ANTHROPIC_BASE_URL
- Kimiapi.moonshot.ai
sk-…c7d2 - DeepSeekapi.deepseek.com
sk-…9b41 - Z.ai GLMapi.z.ai
…0a8e - MiniMaxapi.minimax.io
…f61b
4keys
AutoRouter
Kimi K3.1 ProPro
DeepSeek V4.1 FlashPro
GLM 5.3Pro
MiniMax M3.1 FlashPro
0keys
See what carries over
Have your coding agent switch you over, or paste your Claude Code env, shell profile or aliases here to see what carries over.
Paste it into Claude Code or Codex. It switches you over, carries your rules across and keeps a backup of your old config. It never prints a key.
Stays in your browser. Keys never leave this page.
The env block from ~/.claude/settings.json, the export lines in your shell profile, or the aliases that set ANTHROPIC_BASE_URL for each vendor. Several at once is fine.
Switch me from my direct Kimi, DeepSeek, GLM and MiniMax endpoints to AutoRouter now. Don't ask whether to; I want it done.
1. Read how Claude Code and Codex reach my direct Kimi, DeepSeek, GLM and MiniMax endpoints today: the env block in ~/.claude/settings.json, any .claude/settings.json or .claude/settings.local.json in this project, ANTHROPIC_* lines (exports, aliases and functions) in my shell profiles (~/.zshrc, ~/.zprofile, ~/.bashrc, ~/.bash_profile, ~/.config/fish/config.fish), and [model_providers.*] in ~/.codex/config.toml. Name each vendor by its base URL's host: api.moonshot.ai or api.kimi.com is Kimi, api.deepseek.com is DeepSeek, api.z.ai or open.bigmodel.cn is GLM, api.minimax.io or api.minimaxi.com is MiniMax. People keep one alias or function per vendor, so list every one. Mask every API key to its last four characters before any output reaches this chat, wherever it sits in a line: an alias or a one-line command can set one mid-line, so filter every file you read and never cat or grep one raw. Never print, copy or send a full key.
2. Back up before changing anything: copy each of ~/.claude/settings.json, ~/.codex/config.toml and ~/.codex/auth.json that exists to the same path with .backup-$(date +%Y%m%d) added. Delete nothing.
3. Hand over before AutoRouter writes any settings, so the old setup can't fight it. In ~/.claude/settings.json, remove only these keys from the env block, with jq or python3 and without printing the file: ANTHROPIC_BASE_URL, ANTHROPIC_AUTH_TOKEN, ANTHROPIC_API_KEY, ANTHROPIC_CUSTOM_HEADERS, ANTHROPIC_MODEL, ANTHROPIC_SMALL_FAST_MODEL, CLAUDE_CODE_SUBAGENT_MODEL and every ANTHROPIC_DEFAULT_*_MODEL; also the top-level "model" if it names a model rather than an alias like opus or sonnet. That is your one edit to that file, and the backup undoes it. For the same variables in a project's .claude settings or in my shell profiles, show me each line with its file and line number to remove; don't edit those files. Show the vendor aliases and functions too, since they set these variables for one command. If a vendor's helper wrote them (Z.ai's coding-helper, MiniMax's mmx-cli), say so; don't run it. Then I open a new terminal so the old variables are gone.
4. Set up AutoRouter now by following https://autorouter.com/setup.md, with its rules: I do every sign-in in the browser, you never ask for a password or use sudo, and from here on you never edit ~/.claude/settings.json or ~/.codex/config.toml.
5. Carry my setup over. Get AutoRouter's models: curl -sH "Accept: text/markdown" https://autorouter.com/models. Map each of my models to the AutoRouter model that covers it; a newer version of the same family counts. Write a plain-English rule only for a model setting that says what the model is for: the Opus or subagent model as "Use Kimi K3.1 Pro for planning and reasoning.", the Haiku or small, fast model as "Use DeepSeek V4.1 Flash for background tasks." AutoRouter picks a model for each turn, so the main model and the Sonnet slot need no rule. List the rules for me to add in the AutoRouter app: Routing, then Add a rule. Local models (localhost, Ollama) stay where they are.
6. Finish with setup.md's confirm step, then a short summary: models carried over, rules to add, keys I no longer need, where the backups are, and how to go back (disable each app in AutoRouter's settings, then copy the backups back over ~/.claude/settings.json and ~/.codex/config.toml, and add back the shell lines I removed).
- 0models covered
- 0keys you’d no longer need
- 0model settings replaced
Models
Keys
Routing
Plans
Matched by name against the models on autorouter.com/models. Pro is $50 a month with $20 of usage included; new accounts get a week of Pro, or until $20 of usage is spent.
Questions
What people ask before they switch.
What do the vendors’ own endpoints do well?
Kimi, DeepSeek, Z.ai and MiniMax each give Claude Code an Anthropic-compatible endpoint, so their models run in it with a few variables and no proxy, often with a long context window. Z.ai and MiniMax sell coding plans made for it.
When should I keep a vendor’s key?
Keep it if you’ve paid for that vendor’s coding plan, work on Windows or Linux, or want one model for everything. AutoRouter connects Claude, ChatGPT, Grok and Gemini plans, and runs open models like these on Pro.
Does my config leave my browser?
No. JavaScript in this page reads a paste and sends nothing: no upload, no request. Keys are masked as soon as they’re read, and a key written as $VAR shows only the variable’s name. The agent prompt has your coding agent read your settings on your Mac and mask every key to its last four characters before anything reaches the chat.
What happens to my model settings?
AutoRouter picks a model for each turn, so the main model and the Sonnet slot need no rule. The Opus and subagent models become a rule for planning and reasoning, and the Haiku or small, fast model one for background tasks, such as “Use DeepSeek V4.1 Flash for background tasks.” Your rules go before AutoRouter’s own.
What happens to local models and models AutoRouter doesn’t carry?
A model served on your machine stays where it is. Models are matched by name, ignoring vendor prefixes and snapshot dates, and an older model counts as the newer one AutoRouter carries in its line. Keep the key for any model that isn’t in the list.
Do I lose Claude when I switch?
No. With a vendor’s base URL set, every Claude Code turn goes to that vendor. With AutoRouter, Claude and GPT stay in the picker beside the open models, on your plans first, and AutoRouter sends hard work to the strongest model your plans cover.
Does AutoRouter run on Windows or Linux?
Not yet. AutoRouter is a Mac app for macOS 14 or later. It works in Codex, the Claude Code CLI, Cursor, Claude Desktop, T3 and Terminal.
What does AutoRouter cost?
Free is $0 a month and connects two subscriptions. Pro is $50 a month with $20 of usage included each month, connects any number of subscriptions and adds every other model. New accounts get a week of Pro, or until $20 of usage is spent.