6 people reported
All time, since Sep 15, including 1 thumbs-up on GitHub.
Send button stays disabled in reopened existing chats
“Type a follow-up message — text appears in the composer, but the Send button stays grayed out / disabled and the message cannot be submitted.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/16124/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Typed follow-up text appears in the composer but cannot be submitted after the previous turn completed; restarting the app does not help.
Is this your bug?
File my report- Where
- Desktop app composer
- Error text
markedStreaming=true- Versions
- 26.908.70816 to 26.915.4065.0
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow. Some reports say it used to work.
Part of: Follow-up messages won't send4 bugs
- Follow-up messages cannot be sent40 people
- Second message hangs indefinitely7 people
- Follow-up Send hangs3 people
Not quite your bug?
- Send disabled in new Work chats9 people
Original reports5, newest first
- [Windows Desktop 26.915.4065.0] Send button stays disabled in existing conversations; still reproduces on 26.915 (workaround: switch to Settings page and back)On GitHub#46986
- Windows: reopened chats cannot send follow-up prompts after app/system restart (26.915.4065.0)On GitHub#46814
- macOS: Send button disabled in existing chats while voice input still worksOn GitHub#46440
- Unable to send chat messages in the latest version of the clientOn GitHub#45885
- [Windows][26.908.70816] Restored / existing threads keep Send disabled; only a brand-new chat can send (CLI resume works)On GitHub#45719