You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenAI GPT-5.6 supports reasoning.effort: "max", which corresponds to Codex UI "Ultra". OpenCode Ctrl+T variants for native OpenAI GPT-5.6 models currently stop at xhigh, so users cannot request max effort from the TUI.
There is no max / Ultra variant exposed for GPT-5.6.
Suspected implementation details
ProviderTransform.variants() appears to use openaiReasoningEfforts(). For GPT-5.6-style versions, this currently maps to a list that does not include max. Separately, the OpenAI Responses option handling appears to filter max out of OpenAI reasoning efforts.
Codex exposes "Ultra" for newer models and maps it to request-level max effort. It would be useful for OpenCode to expose the same capability for GPT-5.6 where the provider/model supports it.
I noticed #36141 and #35985 after filing this. This can be closed as a duplicate if maintainers prefer.
One additional implementation concern: PR #35985 appears to improve variant discovery from models.dev metadata, but packages/llm/src/protocols/utils/openai-options.ts also appears to filter max out of OpenAIReasoningEfforts. If that code path is used for GPT-5.6 Responses requests, exposing the variant in the UI may not be sufficient; request validation/serialization may also need to accept and forward reasoning.effort: "max".
So the full expected behavior is:
expose max when the selected model advertises it; and
preserve max through the OpenAI Responses wire path.
Activity
[-]feat(provider): expose reasoning effort "max" for GPT-5.6 (Codex Ultra parity)[/-][+][FEATURE]: expose reasoning effort "max" for GPT-5.6 (Codex Ultra parity)[/+]tlerbao commentedon Jul 11, 2026
I noticed #36141 and #35985 after filing this. This can be closed as a duplicate if maintainers prefer.
One additional implementation concern: PR #35985 appears to improve variant discovery from models.dev metadata, but
packages/llm/src/protocols/utils/openai-options.tsalso appears to filtermaxout ofOpenAIReasoningEfforts. If that code path is used for GPT-5.6 Responses requests, exposing the variant in the UI may not be sufficient; request validation/serialization may also need to accept and forwardreasoning.effort: "max".So the full expected behavior is:
maxwhen the selected model advertises it; andmaxthrough the OpenAI Responses wire path.github-actions commentedon Jul 11, 2026
Thanks for updating the issue! It now follows our contributing guidelines.