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
Subagent model_reasoning_effort config is ignored on Codex App #27624
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.608.12217 • Released Jun 9, 2026
What subscription do you have?
Pro
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
After recent Codex App update, whenever an subagent I defined under ~.codex\agents is spawned, if I work in Codex App, the subagent spawned will always be set with "medium" reasoning effort.
I tried in VS Code Codex Extension, it works normally. It can spawn subagents in configured model_reasoning_effort instead.
What steps can reproduce the bug?
Define whatever subagent, set its model_reasoning_effort to "high" or "xhigh".
Then ask Codex App to spawn the defined subagent.
You will see the subagent spawned with "medium" reasoning no matter how you set the model_reasoning_effort subagent config.
What is the expected behavior?
The model_reasoning_effort inside subagent config should be followed when that subagent is spawned.
Additional information
Only problem in Codex App. VS Code Extension works fine.
The Codex App also no longer directly show the reasoning effort at bottom statusline when opening subagent. I need to click /reasoning to see the reasoning in the subagent thread.
That issue is talking about Codex CLI TUI interaction issue. My issue is
talking about
subagent model_reasoning_effort ignore in Codex App. These are two totally
different issues.
「github-actions[bot] ***@***.***>」在 2026年6月11日 週四,下午11:58 寫道:
Activity
github-actions commentedon Jun 11, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
joecklau commentedon Jun 11, 2026
joecklau commentedon Jun 12, 2026
Tested fixed in Version 26.609.30741 • Released Jun 11, 2026