Skip to content

There's an issue with the selected model - CC Switch

Quick fix

Check the model name and provider config in cc-switch. The model test is unreliable — go by an actual request.

Error output
● There's an issue with the selected model  (claude-sonnet-4-5-20250929). It may not exist or you may not

This cluster holds several problems around model switching and model configuration. The most typical: after switching or connecting a third-party API, Claude Code reports the selected model does not exist or is unavailable, while the same API works in other tools but errors in a terminal connected through cc-switch. It usually comes down to the model name, provider compatibility, a proxy, or an unreliable model test result. Maintainers explain the model test feature is hard to adapt to every provider, so treat its result as indicative and go by an actual request. Other variants: the model test failing with max_tokens value 1 is below minimum allowed 2; the v3.12.0 portable build showing only variable names in the model test; unreplaced {{providerName}} and {{message}} placeholders in the test message; the model field being undeletable or the UI blank while editing a provider; variants written incorrectly under options in OpenCode; and a model switch replacing setting.json wholesale so config outside env cannot be shared.

  1. Confirm the selected model name matches what the provider actually supports, and avoid model names the provider does not offer or has deprecated.

  2. Do not rely on the cc-switch model test button alone. If the test fails but real calls work, go by the actual request.

  3. If you use OpenCode and need to configure reasoning effort, upgrade to v3.12.3 or newer. Older versions put variants under options incorrectly; the correct location is models.<model_id>.variants.

    OpenCode 配置文件
    "models": {
    "gpt-5.2": {
    "variants": {
    "low": {
    "reasoningEffort": "low"
    }
    }
    }
    }
  4. If you see {{providerName}} check failed: {{message}}, upgrade to v3.12.1 or newer — that i18n placeholder problem was fixed there.

  5. If a model switch loses config outside env in setting.json, use the cc-switch general config / sync config feature so the whole file is not replaced.

ToolUnknown
VersionUnknown
PlatformsUnknown
Why does the same API work in the Roo Code plugin but report a model problem in a terminal opened from cc-switch?
The model name, provider compatibility, or request path may differ. Confirm the model name configured in cc-switch matches what the provider supports, then verify with a real request rather than the model test alone.
The model test reports max_tokens value 1 is below minimum allowed 2. What now?
The model test parameters are incompatible with some third-party providers. Maintainers explain the model test is unreliable and you should go by an actual request — a failed test does not mean the model is unusable.
Why did variants become options.variants in OpenCode?
The older cc-switch UI wrote variants under options incorrectly. From v3.12.3 on, OpenCode model variants sit at the top level and display correctly.
Does a model switch overwrite the rest of my setting.json?
Users report the old behaviour replacing all of setting.json, so config outside env could not be shared. Later versions added general config / sync config for preserving shared configuration.

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.