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 mobile expands reasoning traces by default; should match desktop collapsed behavior #23250
Codex desktop keeps reasoning/thinking sections collapsed by default, with click-to-expand. That behavior is good.
On Codex mobile in the ChatGPT app, the full reasoning trace is expanded by default. For long high/xhigh Codex sessions, this makes the thread extremely hard to read and slows down review work.
Expected behavior:
Keep reasoning collapsed by default on mobile, same as desktop.
Allow tap-to-expand when I want to inspect it.
Do not reduce reasoning effort or remove the trace; this is only a presentation issue.
This is especially important for users running high/xhigh reasoning, where the reasoning block can dominate the entire mobile screen.
Supporting consistency with desktop here, from the third-party-model side: with a custom provider, desktop renders the reasoning summary collapsed with tap-to-expand, plus the tool-call middle section. On mobile remote the same thread either expands the trace flatly or loses the middle section depending on where the thread was created (see #31370 for the mobile-created-thread divergence). A collapsed-by-default, tap-to-expand presentation matching desktop would be the right fix — and it should apply consistently to custom-provider threads too, not just native OpenAI ones.
Activity
ropepop commentedon Aug 10, 2026
Supporting consistency with desktop here, from the third-party-model side: with a custom provider, desktop renders the reasoning summary collapsed with tap-to-expand, plus the tool-call middle section. On mobile remote the same thread either expands the trace flatly or loses the middle section depending on where the thread was created (see #31370 for the mobile-created-thread divergence). A collapsed-by-default, tap-to-expand presentation matching desktop would be the right fix — and it should apply consistently to custom-provider threads too, not just native OpenAI ones.