[Windows] Composer is not cleared and UI stalls after every message send

Open
#33,499 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
desktop

Research direction

Start by reproducing the issue in the Codex Desktop Windows message-submission and composer flow using the listed steps. Trace the submission entry point and response-start handling to determine why the composer retains text and the UI stalls. Done means the composer clears after successful submission and the UI remains responsive while the response streams.

Written by the indexing model from the issue text.

Description

app bug performance windows-os
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
  1. Open Codex Desktop on Windows.
  2. Start or open a Codex conversation.
  3. Send a short plain-text message.
  4. Observe that the message appears in the conversation but remains in the composer.
  5. 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.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.