[macOS Desktop] Composer text remains after Send / Steer instead of clearing after recent update
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What issue are you seeing?
After the recent Codex Desktop update, the composer/input box does not reliably clear after submitting text.
When I:
- send a normal prompt, or
- use Steer while a task is running,
the submitted text can remain visible inside the text box instead of being cleared.
This makes the UI ambiguous because it is difficult to tell whether the text was successfully submitted, is still pending in the composer, or needs to be sent again. It can also lead to accidental duplicate submissions or editing text that has already been sent.
The issue appeared after the recent update and persists after restarting Codex multiple times.
Steps to reproduce
- Open Codex Desktop on macOS.
- Open an existing project/thread.
- Enter text in the composer.
- Send the message, or use Steer while Codex is working.
- Observe that the submitted text can remain in the composer instead of being cleared.
- Repeat with additional prompts/Steer messages; the behavior recurs.
Actual behavior
Submitted text remains visible in the input box after Send / Steer.
Expected behavior
Once Codex accepts a Send or Steer action, the composer should immediately clear the submitted text. If submission fails, the UI should clearly indicate failure and preserve the draft intentionally rather than leaving the composer in an ambiguous state.
Additional context
- The problem started after the recent Codex Desktop update.
- Multiple full app restarts have not resolved it.
- The same user is also experiencing frequent timeout / reconnect behavior after the update; an independent reproduction has been added to #37660. The composer-clearing problem is reported separately because it is a distinct UI/state issue.
- Exact Codex Desktop build number can be added if needed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior in Codex Desktop on macOS using both Send and Steer, including repeated submissions. Trace the composer handling for those actions; done means accepted text clears immediately, while failed submission preserves the draft with a clear failure indication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100