What version of the Codex App are you using?
26.707.9981.0 (Microsoft Store)
What platform is your computer?
Windows 11 x64
What issue are you seeing?
In Codex Desktop, every submitted message is delivered and appears in the conversation, but the composer does not clear. The exact submitted text remains in the input box while the UI stays on “Thinking” and becomes temporarily unresponsive.
This makes the message look unsent even though the conversation already contains it. The stall occurs after every message send, including short plain-text messages in a normal Codex conversation; it is not limited to Browser, Chrome, or Computer Use.
A screenshot is available showing the message bubble already present above the composer while the same text remains in the composer and the app is stuck on “Thinking”.
Steps to reproduce
- Open Codex Desktop on Windows.
- Start or open a Codex conversation.
- Send a short plain-text message.
- Observe that the message appears in the conversation but remains in the composer.
- Observe that the UI stalls temporarily while showing “Thinking”.
Expected behavior
- The composer should clear immediately after successful submission.
- The UI should remain responsive while the response begins streaming.
Actual behavior
- The message is delivered and displayed in the conversation.
- The composer retains the submitted text.
- The UI remains in “Thinking” and stalls temporarily after every send.
Additional context
This appears distinct from the bundled Browser/Chrome/Computer Use runtime relocation issue reported in #32732. The affected installation is the Microsoft Store package and has also exhibited Windows rendering/plugin-runtime problems.
What version of the Codex App are you using?
26.707.9981.0 (Microsoft Store)
What platform is your computer?
Windows 11 x64
What issue are you seeing?
In Codex Desktop, every submitted message is delivered and appears in the conversation, but the composer does not clear. The exact submitted text remains in the input box while the UI stays on “Thinking” and becomes temporarily unresponsive.
This makes the message look unsent even though the conversation already contains it. The stall occurs after every message send, including short plain-text messages in a normal Codex conversation; it is not limited to Browser, Chrome, or Computer Use.
A screenshot is available showing the message bubble already present above the composer while the same text remains in the composer and the app is stuck on “Thinking”.
Steps to reproduce
Expected behavior
Actual behavior
Additional context
This appears distinct from the bundled Browser/Chrome/Computer Use runtime relocation issue reported in #32732. The affected installation is the Microsoft Store package and has also exhibited Windows rendering/plugin-runtime problems.