Extension Thinking Processes Colapsed by Default
Resolved 💬 5 comments Opened Mar 4, 2026 by teron131 Closed Mar 4, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the IDE extension are you using?
0.4.79
What subscription do you have?
ChatGPT Plus
Which IDE are you using?
Cursor / Windsurf
What platform is your computer?
macOS Tahoe 26.2
What issue are you seeing?
Codex extension now collapses the thinking... / process section is now collapsed by default, requires manual expand every turn. No settings seem to affect it.
I did not intentionally change settings related to this behavior, and this started happening only recently.
Current relevant config values in ~/.codex/config.toml:
model_reasoning_summary = "auto"
hide_agent_reasoning = false
show_raw_agent_reasoning = true
Relevant extension setting:
"chatgpt.cliExecutable": "codex"
Are my settings wrong, or the recent changes bugged?
What steps can reproduce the bug?
Just use.
What is the expected behavior?
_No response_
Additional information
_No response_
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I don't know if this is involved with the issue you're reporting, but why are you setting
chatgpt.cliExecutable? That's intended for debugging purposes, and we don't recommend using it under normal circumstances. It will cause the extension to use a version of the CLI that it's not tested with.The other three settings that you mentioned above affect the TUI, not the extension. So that explains why they have no effect.
I think the recent change for collapsing the thinking by default was intentional. I'll need to check with our designer. If you'd like to see a different behavior, please open a feature request.
@etraut-openai Thanks.
chatgpt.cliExecutableis set by Codex trying to fix. I didn't change my settings and have the bug. It is not just collapsed, but also not updating until a click or completed. Anyway, I also see some other people mention this bug and namely fixed but still happen for me.Ah, yes that's a known issue. I think it's fixed in the latest prerelease. Could you try switching to the prerelease version and confirm?
I confirmed that this was an intentional change. All thinking processes other than the last one are now collapsed. The previous behavior led to significant performance issues in some cases, and this is a workaround. We're looking at other ways to mitigate the performance issues through session virtualization in the future. If that's successful, we will consider reversing this behavioral change.