API Error: 400 invalid request: Claude Desktop model route is not configured - Claude Desktop
Quick fix
Upgrade cc-switch to v3.16.0+ and configure routing rules explicitly for sub-task models such as Haiku and Opus on the provider form.
Symptom
Section titled “Symptom”API Error: 400 无效的请求: Claude Desktop 模型路由未配置: claude-haiku-4-5-20251001 (Claude Desktop model route is not configured: claude-haiku-4-5-20251001)API Error: 400 invalid request: Claude Desktop model route is not configured: claude-haiku-4-5-20251001 (Claude Desktop model route is not configured: claude-haiku-4-5-20251001)
In Claude Desktop Agent or Code scenarios, the system calls different models automatically — Sonnet/Opus for the main task, Haiku for sub-tasks or lightweight work. If the cc-switch proxy layer only has routing configured for the main model, without Haiku, Opus, or other internally called models in the routing rules, or if the model name and the channel allowlist do not line up, this route-not-configured error fires. It can also appear in JSON form, reporting the claude-opus-4-7 route as not configured.
Upgrade cc-switch to v3.16.0 or newer, which fixed this and supports date aliases such as claude-haiku-4-5-20251001.
On the Claude Desktop provider form in cc-switch, edit and configure the route id for Opus, Sonnet, and Haiku explicitly, mapping each to its upstream model, and make sure the model name, channel allowlist, and actual provider model line up.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 3 real issues
- Why does the main model work while Agent mode errors?
- Agent mode triggers sub-tasks automatically and calls lightweight models such as Haiku. With routing configured only for the main model, the proxy layer cannot handle those unconfigured model requests. Add routing rules for Haiku and the others explicitly.
- I configured the Haiku model — why does routing still error?
- Usually the model name, channel allowlist, and actual provider model do not line up. Make sure the matching route id is configured explicitly on the provider form, and upgrade to a version that supports date aliases.
Related problems
Section titled “Related problems”This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.