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
{{ message }}
Repository navigation
Codex Desktop new-chat reasoning selector does not apply to initial prompt #21093
In Codex Desktop, the new-chat reasoning selector appears to accept a change from low to xhigh before the first prompt is submitted, but the first request is still sent with reasoning_effort: "low". Follow-up prompts in the same thread do appear to honor reasoning changes.
Environment
Product: Codex Desktop on macOS
App version: 26.429.30905 / bundle 2345
CLI/session version observed: codex-cli 0.128.0
Model: gpt-5.5
Config:
model = "gpt-5.5"model_reasoning_effort = "xhigh"service_tier = "fast"
Steps to reproduce
Start a new chat in Codex Desktop.
Observe the reasoning selector is preselected as low.
Before submitting the initial prompt, change reasoning to xhigh.
Submit the initial prompt.
Inspect the session JSONL / request logs for the first turn.
Expected behavior
The initial request should be sent with reasoning_effort: "xhigh" because the user changed the new-chat selector before submitting. This should also align with model_reasoning_effort = "xhigh" in ~/.codex/config.toml.
So this does not appear to be a purely visual UI issue; the backend request actually used low reasoning.
Additional notes
Follow-up prompts in the same thread can successfully change reasoning effort.
service_tier = "fast" is configured intentionally; this should select the fast service tier, not force reasoning_effort = "low".
The issue seems specific to the new-chat initial prompt path, possibly the Desktop app composer state not applying the pre-submit reasoning selector value to the first turn.
Closing as a duplicate. The behavior reported here is covered by #20364, and #20634 has additional closely matching evidence around the Codex Desktop new-composer Intelligence/reasoning dropdown getting stuck before the first message. The extra detail from this report is that the first request log also showed the backend request being sent with reasoning_effort: "low", so this was not only a visual selector issue.
Activity
github-actions commentedon May 4, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
tylerwisdom-logimon commentedon May 4, 2026
Closing as a duplicate. The behavior reported here is covered by #20364, and #20634 has additional closely matching evidence around the Codex Desktop new-composer Intelligence/reasoning dropdown getting stuck before the first message. The extra detail from this report is that the first request log also showed the backend request being sent with
reasoning_effort: "low", so this was not only a visual selector issue.