Skip to content
CC Switch WikiUnofficial Community Wiki

The 'gpt-6-sol' model is not supported - Claude Code

Quick fix

Update the Codex OAuth reported client version to one supported by the model and rebuild, or temporarily use gpt-5.6-sol / gpt-5.6-luna.

Symptom

Section titled “Symptom”
Error output
上游错误 (400): {"detail":"The 'gpt-6-sol' model is not supported when using Codex with a ChatGPT account."}
English translation

Upstream error (400): {"detail":"The 'gpt-6-sol' model is not supported when using Codex with a ChatGPT account."}

Cause

Section titled “Cause”

CC Switch pins the Codex OAuth client version to `0.153.4` for `/responses` forwarding and `/models` discovery. Evidence shows that with the same account and endpoint, `gpt-6-sol` returns 400 at `version: 0.153.4` but 200 at `0.155.0`; the `gpt-6.1-sol` model catalog appears starting with `0.159.0`.

Therefore, newer GPT-6 Sol/Luna models may be rejected or undiscoverable because the OAuth request reports a version that is too old. For `gpt-6.1-sol`, current evidence confirms that the catalog depends on the version, but does not directly confirm that updating removes the `/responses` 400.

Fix

Section titled “Fix”

  1. Use a build containing an updated Codex OAuth client version. If building from source, update `CODEX_OAUTH_CLIENT_VERSION` to the compatible version required by the target model, then rebuild.

    src-tauri/src/proxy/providers/codex_oauth_auth.rs
    pub(crate) const CODEX_OAUTH_CLIENT_VERSION: &str = "0.153.4";
    pub(crate) const CODEX_OAUTH_CLIENT_VERSION: &str = "0.155.0";

  2. If you cannot update the build yet, temporarily change the model mapping in Claude back to `gpt-5.6-sol` or `gpt-5.6-luna`.

  3. For `gpt-6.1-sol`, after updating, verify separately that it appears in the model list and whether actual generation requests still return HTTP 400.

Affected Versions

Section titled “Affected Versions”
ToolClaude Code
Version3.20.4（受影响）
PlatformsWindowsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 4 real issues

FAQ

Section titled “FAQ”
Why do manually configured 6-sol and 6-luna fail in claude?
A known cause is that the Codex version reported by the Codex OAuth request is pinned to `0.153.4`, below the verified `0.155.0` threshold for `gpt-6-sol`; users have reported that updating the version and rebuilding resolves it.
Why can't CC local authentication retrieve gpt-6-sol even though all versions say they are current?
Model discovery also uses the pinned Codex reported version, so having a newer local Codex CLI does not mean that CC Switch OAuth model discovery requests also use a newer version.
Section titled “Related problems”
Gateway /v1/models returned an unexpected body: Claude CodeNo verified solution is available; the local proxy must return an Anthropic `data` model-list format to Claude Code.1 issues merged{"models":[]}: Codex OpenAI official proxy model catalog is emptyTemporarily place the Codex-format catalog file inside CODEX_HOME and reference it in config.toml; the official proxy forwarding fix is unconfirmed.1 issues mergedUpstream HTTP 404 - DeepSeekResolve based on the scenario: if the endpoint path is the issue, complete the API address with the full API root (such as `.../v1`); if the model… (cc-switch)6 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.