openai / openai/codex

Codex Windows: Send Button Stays Disabled After a Completed Turn

Open
#46,619 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

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

26.915.31945

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

On Codex Desktop for Windows (and on two devices), after a response completes, I can type a follow-up message but the Send button becomes grey/disabled and the message cannot be submitted.

The issue persists after restarting, reinstalling from the Microsoft Store, and updating to the latest version. The conversation itself is still usable from ChatGPT on iOS, which suggests the problem is specific to the Windows desktop client.

What steps can reproduce the bug?

Feedback ID: 01a0b912-20d3-7993-9af4-971fcb365af8

What is the expected behavior?

No response

Additional information

No response

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.

Research direction

Start with the Windows desktop client and the reported Feedback ID 01a0b912-20d3-7993-9af4-971fcb365af8. Reproduce a completed turn, type a follow-up, and verify why the Send button remains disabled; done means the follow-up can be submitted after the response completes.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.