Codex responses are fully nested within collapsed <Worked for {N}s> sections

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.513.31313 (2867)

What subscription do you have?

Plus

What platform is your computer?

Darwin 21.6.0 arm64 arm

What issue are you seeing?

Codex's responses are sometimes (e.g. in every message in a chat I'm running now) fully contained within <Working> blocks, with no response text outside them. After Codex finishes its response, I need to click the Worked for 5s title to expand the block and actually see the response.

On the flipside, last week I experienced Codex writing its final response within a <Working for {N}s> block, and then ending the <Working for {N}s> block and also writing out its almost-exactly-the-same direct response to me outside the block. So essentially producing 2x more output tokens (and taking 2x longer to respond) than necessary with an unneeded Working block.

What steps can reproduce the bug?

1. Open a chat
2. Send a message
3. Wait for Codex to finish responding and see its response may be fully collapsed within a <Worked for {N}s> block

What is the expected behavior?

The <Worked for {N}s> block only contains actually-needed thinking/working that Codex does, that makes sense as behind-the-scenes work to keep collapsed. Its direct response to me should be fully visible outside that collapsible Working block.

Additional information

Related: implementing #22334 would reduce the friction this bug causes (i.e. needing to click to expand the Working block to see Codex's response to me) when the response is fully hidden within the Working block.

Although it wouldn't solve the 2x token usage and 2x latency when Codex also duplicates its response outside the Working block.