Desktop app: assistant response stays hidden until UI click
Resolved 💬 3 comments Opened Feb 28, 2026 by BrokenShell Closed Feb 28, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
In the Codex desktop app, after sending a message, the assistant response appears to stall indefinitely until I click somewhere in the UI. As soon as I click, the pending response immediately appears.
Steps to Reproduce
- Open Codex desktop app.
- Send a prompt in an active thread.
- Wait for the model response without interacting with the UI.
- Observe that no response renders while idle.
- Click anywhere in the app window.
- Observe the response immediately appears after the click.
Expected Behavior
Responses should render/stream without requiring any manual UI interaction.
Actual Behavior
Response appears only after a click or focus interaction.
Frequency
Frequent (enough to be reliably noticeable during normal use).
Workaround
Clicking in the UI causes the response to show up.
Impact
Feels like requests are hanging and interrupts normal workflow because I need to "poke" the UI to see output.
3 Comments
Environment details:
26.227.1448(build747)26.3(build25D125)25.3.0,arm64Extra note:
0.99.0(not sure if relevant to desktop rendering, but included for completeness).Behavior remains: assistant response appears only after a UI click/focus interaction.
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Closing as a duplicate of #13106 (and also similar to #13133).\n\nThanks for the review bot nudge; I’ve subscribed to those issues for updates.