There's an issue with the selected model — model mapping failure - CC Switch
Quick fix
Upgrade CC Switch, restart the target tool, and start a new session so local routing strips the [1m] suffix and rematches the mapping.
Symptom
Section titled “Symptom”There's an issue with the selected model (claude-haiku-4-5[1m]). It may not exist or you may not have access to it. Run --model to pick a different model.With a 1M context or in some mapping scenarios, Claude Code and Claude Desktop send the model name with a [1m] suffix, for example claude-haiku-4-5[1m]. Older cc-switch local routing matched that raw model name against the routes on the provider (claude-haiku-4-5), so nothing matched, model mapping never ran, and Claude Code reported that the selected model may not exist. A maintainer explained in issue #3588 that the trailing [1m] is now stripped at runtime before model mapping.
The same family extends to incomplete or overwritten config writes after switching or editing a provider for Codex/Hermes/OpenCode: model_provider forced back to ccswitch (#2934/#3029), the Codex model name still holding its old value (#5229/#3416/#6225), Hermes base_url/api_key not updating (#4176), OpenCode small_model disappearing (#3856), settings.json not overwritten (#2539). All of these point at the same config-overwrite path. The issues sometimes contradict each other — #5591 argues the UI only shows the internal Claude model name and does not necessarily indicate a real mapping error — so when troubleshooting, check the model name actually sent upstream.
Upgrade CC Switch to the latest version, at minimum one containing the #3588 fix that strips the [1m] suffix, plus the Codex/routing fixes in #3029/#3999/#4996.
Quit and restart CC Switch and Claude Code / Claude Desktop / Codex completely. An existing Claude Code session may still cache the wrong model name, so start a new session and try again.
Switch the target provider once more in CC Switch. If the target app is Codex/Hermes/OpenCode, open its actual config file and confirm model_provider, base_url, api_key, and small_model now hold the new values; fill in anything missing by hand, or switch again.
If the problem only appears in VS Code plugin sessions, restart VS Code or start a new session — older plugin versions do not hot-reload model config (#4269).
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 23 real issues
- #1162[Bug] v3.11.0 cc-switch 插件将 Opus 模型请求重定向至 Sonnet 模型
- #2539使用CC-switch切换模型后，settiong.json文件并没有被覆盖
- #2777配置了多个token ,经常串。 已切换什么的，就换成另一个，配置都丢失.
- #2934codex model_provider被强制修改为ccswitch；导致不显示历史记录
- #3029无法更改codex的model_provider配置
- #3178ccswitch+hermes模型使用问题
- #3388claude code 映射Mimo的时候显示找不到模型，我已开启了路由，并且之前一直都是可以正常使用的
- #3416codex是不是不能换模型
- #3474codex 接管 Live 配置失败，尝试恢复: 写入 Codex 配置失败: Codex model catalog template `gpt-5.5` not found. Please start Codex once so models_cache.json is available, or ensure the `codex` CLI is on PATH.
- #3526claude desktop和codex同时打开，在claude desktop中提问会报参数错误
- #3588Claude Desktop 3P 对话中切换模型会无法映射
- #3856opencode的配置项需要加上small_model否则无法命名会话
- #3891切换不同供应商的api
- #3982harmes无法更改供应商名称、无法选择模型
- #3999路由配置使用不了最新claude模型
- #4176Hermes base_url and api_key not updated when switching models via CC-switch
- #4269VS Code + Claude Code 插件使用（Calcude Code），更换模型服务商后，会话模型没有热重载
- #4876讯飞平台接入的模型，经常无法被正常转换
- #5229codex接火山codingplan折腾了一个小时还是404，开发团队到底有没有注意到问题，太气人了
- #5290配置模型映射错误
- #5591CC Switch3.17.0模型映射错误
- #6225CC配置了大模型，codex获得不全
- #6261需要显式设置full模式。url自动拼接 chat/complation导致请求模型失败，需要去改配置开启full模式，可以每次编辑供应商又回回到 自动拼接的模式
- The session reports this selected model error right after I upload an image. Why?
- In #3388 a user reported this error triggered after uploading one image, and a new session recovered it. It is related to the [1m] model name failing to match, not necessarily to broken image support.
- I changed the model in CC Switch — why does Codex still use the old model name?
- Older versions may not update model_provider or the model catalogue when writing Codex config. Upgrade, switch once more, and check the actual config file.
- The mapping error shows an internal Claude model name. Does that mean mapping failed?
- A maintainer explained in #5591 that a failed request records the internally mapped Claude model name, which does not necessarily indicate a real mapping error. Check the model name actually sent upstream.
- Do I have to restart the VS Code plugin after switching provider?
- #4269 reports that older versions needed a VS Code restart to hot-load the model. If it still happens after upgrading, try restarting or starting a new session.
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.