Skip to content
CC Switch WikiUnofficial Community Wiki

selected model (kimi-k2.5) may not exist error - Claude Code

Quick fix

Remove the trailing /v1 from the API address and use the Anthropic-compatible interface. If an old session contains images, run /compact or switch models.

Symptom

Section titled “Symptom”
Error output
There's an issue with the selected model (kimi-k2.5). It may not exist or you may not have access to it. Run /model to pick a different model.

Cause

Section titled “Cause”

When configuring third-party providers such as Kimi or Alibaba DashScope, proxy errors can result from the API address format, model context limits, or User-Agent validation. The most common error is Claude Code reporting that the model does not exist. This is usually caused by an extra /v1 at the end of the API Base URL or by sending images in an old session that some Kimi models, such as kimi-k2.5-pro, do not support.

This issue cluster also includes several other variants: (1) the upstream API does not return token statistics, so CC Switch shows 0 in its backend (Issue #881); (2) Codex's default User-Agent is rejected with a 403 by the Kimi Coding interface (Issue #3559); (3) a logic error when Codex converts reasoning history causes a Kimi K3 task to stop midway (Issue #5506).

Fix

Section titled “Fix”

  1. Check the provider API Base URL in CC Switch. If it ends with /v1, remove that suffix.

  2. If you use Alibaba DashScope, make sure you select or configure the Anthropic-compatible API interface.

  3. If the error occurs in an old session, its context may contain images the model does not support. In Claude Code, run /compact to compress the context, or switch to a model that supports vision, such as kimi-k2.5.

  4. (For Codex users) If you encounter a 403 rejection or a task that stops midway, update CC Switch to v3.16.3 or later, then set the User-Agent override to claude-cli/* in the provider configuration.

Affected Versions

Section titled “Affected Versions”
ToolClaude Code
Versionv2.1.72
PlatformsWindowsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 4 real issues

FAQ

Section titled “FAQ”
Why does a new session work, while an old session reports a selected model error?
The old session's context may contain images, which some models, such as kimi-k2.5-pro, do not support. Run /compact to compress the context or switch to a model that supports images.
Why does CC Switch show 0 for all input and output token statistics in its backend?
The upstream provider's API response, such as Kimi or Alibaba DashScope's, does not include token statistics. This is an upstream interface issue and does not affect actual use.
What should I do if Codex reports a 403 when using the kimi-for-coding model?
The Kimi Coding interface blocks User-Agent values that are not allowlisted. Update CC Switch to v3.16.3 or later, then set the User-Agent override to claude-cli/* in the provider configuration.
Section titled “Related problems”
Only under the OpenCode agentUpdate to v3.16.4 or later to use OpenCode Go presets with API Key-only configuration in Claude Code, Claude Desktop, Codex, and OpenCode.1 issues mergedKimi balance query unavailableUpdate cc-switch to the latest version; the backend has automatically fixed Kimi balance recognition.2 issues mergedCodex Kimi HTTP 400 moonshot flavored json schemaUpgrade CC Switch to the latest version; the proxy automatically cleans Kimi-incompatible `$ref` sibling keywords and tool schemas missing root-level `type`.8 issues merged

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.