level "max" not supported, Codex Desktop
Quick fix
Select max for gpt-5.6-sol in Codex Desktop; ultra is not a separate reasoning effort.
Symptom
Section titled “Symptom”CC Switch local proxy failed while handling Codex endpoint /responses.
Provider: <redacted>; model: gpt-5.6-sol;
upstream_status: HTTP 400;
cause: level "max" not supported, valid levels: low, medium, high, xhighIn the report, Codex Desktop shows ultra on the native slider for gpt-5.6-sol, while a /responses request through the cc-switch local proxy returns level "max" not supported at the highest setting. The reporter suspected ultra may be mapped or normalized to max in the request path, but the original post provides no verifiable root-cause conclusion.
The maintainer explains that ultra is not a separate reasoning effort; it is max plus additional prompt injection. max is currently selectable, so there are no plans to implement ultra as a separate capability. This explains product semantics; it does not indicate that the proxy HTTP 400 in the original report was separately fixed.
Select `max` for gpt-5.6-sol in Codex Desktop; do not configure `ultra` as a separate reasoning effort.
If `max` does not produce the same behavior as `ultra`, reopen the source issue as requested by the maintainer and provide a comparison with the official model directory.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 1 real issues
- Can I select max?
- Yes. The maintainer states that `max` is currently selectable.
- Is ultra a separate reasoning effort?
- No. The maintainer states that `ultra` is `max` plus additional prompt injection and will not be implemented separately.
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.