Skip to content
CC Switch WikiUnofficial Community Wiki

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

Quick fix

Drop the trailing /v1 from the API address and use the Anthropic-compatible endpoint. For an old session with images, /compact or switch model.

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”

Configuring a third-party provider such as Kimi or Alibaba DashScope produces several proxy anomalies, from endpoint address format, model context limits, and User-Agent validation. The most common — Claude Code reporting the model does not exist — usually comes from an extra trailing /v1 on the API Base URL, or from sending an image in an old session to a Kimi model such as kimi-k2.5-pro that does not support them.

The cluster also holds other variants: 1) upstream not returning token statistics, leaving CC Switch backend data at 0 (Issue #881); 2) the default Codex User-Agent being rejected by the Kimi Coding endpoint with a 403 (Issue #3559); 3) a logic error converting reasoning history in Codex stopping a Kimi K3 task mid-way (Issue #5506).

Fix

Section titled “Fix”

  1. Check the provider API Base URL in CC Switch and remove a trailing /v1 if present.

  2. On Alibaba DashScope, make sure you select or configure the Anthropic-compatible API endpoint.

  3. If the error appears in an old session, the context may contain images the model does not support. Run /compact in Claude Code to compact the context, or switch to a vision-capable model such as kimi-k2.5.

  4. (Codex users) For a 403 rejection or a task stopping mid-way, update CC Switch past v3.16.3 and override the User-Agent to claude-cli/* in the provider config.

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 it work in a new session but report the selected model error in an old one?
The old session context may contain images, which some models such as kimi-k2.5-pro cannot read. Use /compact to compact the context, or switch to a model that supports images.
Why are the input and output token statistics in the CC Switch backend all 0?
The upstream provider (Kimi or Alibaba DashScope) did not include token statistics in its API response. That is an upstream endpoint problem and does not affect actual use.
Codex reports 403 with the kimi-for-coding model. What now?
The Kimi Coding endpoint blocks User-Agents that are not allowlisted. Update CC Switch to v3.16.3 or newer and override the User-Agent to claude-cli/* in the provider config.
Section titled “Related problems”
Codex connecting to Kimi reports HTTP 400 tool schema validation failureUpgrade cc-switch to v3.18.0+; if the error persists, wait for the MFJS schema cleaning feature to go live.7 issues mergedEGL_BAD_PARAMETER white screen error - cc-switchInstall the native .deb or AUR package instead, or run the AppImage with LD_PRELOAD pointing at the system library, to resolve the ABI conflict.6 issues mergedBash(...) Waiting... Claude CodeDowngrade Claude Code to v2.1.104 or v2.0.64 (admin required), or switch to a compatible provider such as Alibaba Cloud Bailian.1 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.