Codex Desktop on macOS frequently becomes unable to type in the composer after switching away to another app and switching back.

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

Latest Version

What subscription do you have?

gpt plus

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

Codex Desktop on macOS frequently becomes unable to type in the composer after switching away to another app and switching back.

Environment:

• Product: Codex Desktop, not CLI
• OS: macOS
• Date observed: 2026-06-27
• Bundled Codex CLI reported: codex-cli 0.142.3
• No in-app browser, pop-out window, floating overlay, or extra Codex window intentionally opened

Reproduction pattern:

1. Use Codex Desktop normally in a thread.
2. Switch to another macOS app.
3. Switch back to Codex Desktop.
4. The message input/composer is often stuck and cannot accept typing.
5. Restarting Codex Desktop temporarily fixes it, but the issue happens frequently.

Impact:
This is happening often enough to seriously affect normal usage. I frequently have to restart Codex Desktop just to continue typing.

Local logs showed suspicious UI/app-server state synchronization errors around the same period, including:

• "Received turn/started for unknown conversation"
• "Received turn/completed for unknown conversation"
• "No promise for request ID"
• long app/list response durations around 53-58 seconds
• earlier "EPIPE" followed by app server disconnect

Expected behavior:
After switching away from Codex Desktop and switching back, the composer should remain focusable and accept keyboard input normally.

Actual behavior:
The composer sometimes becomes unusable and cannot accept input until Codex Desktop is restarted.

What steps can reproduce the bug?

Feedback ID: 019f0807-5107-79c1-b302-8434c03e807f

What is the expected behavior?

_No response_

Additional information

_No response_