55 people reported

All time, since Sep 14, including 18 thumbs-up on GitHub.

Follow-up messages won't send

“However, after Codex finishes responding to the first turn, the Send button becomes a dim/disabled upward arrow.”

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/themes/118/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

Fading. No reports and thumbs-up in the last 7 days and 1 the week before, down from 41 a week at the late-September peak.

4 bugs in this theme

  1. Follow-up messages cannot be sentHas a workaround40 people
  2. Second message hangs indefinitelyHas a workaround7 people
  3. Send button stays disabled in reopened existing chatsHas a workaround6 people
  4. Follow-up Send hangsHas a workaround3 people

What's included

  • After the first response completes, Send stays greyed out while text sits in the composer
  • Clicking Send on a follow-up leaves the button spinning and the message never appears
  • Reopened or existing chats cannot send after an app or PC restart, on Windows and macOS
  • Logs show no turn/start for the follow-up, plus 'Conversation state not found' or 'turn/completed for unknown conversation'
  • Switching to another chat or Settings and back, voice input, or tool-sent follow-ups still work

Not included

  • The first prompt of a new Work conversation cannot be sent while existing chats work
  • Messages fail to send in the web version

Original reports38, newest first

  1. Codex Windows App – Follow-up messages get stuck on sending and are never submittedOn GitHub#58039
  2. Codex Desktop hangs indefinitely from the second message onwardOn GitHub#48689
  3. [Windows] Cannot submit a second message in Codex after the first turn completesOn GitHub#48180
  4. [Windows Desktop 26.917.9434.0] Follow-up messages cannot be submitted; Send stays busy or disabled and no turn/start is dispatched1On GitHub#48140
  5. [Windows Desktop 26.917.9434.0] Follow-up messages cannot be submitted; Send stays busy or disabled and no turn/start is dispatchedOn GitHub#48136
  6. Windows: app freezes on the second message; CLI and app-server workOn GitHub#48133
  7. no-active-thread-01a0d896-a90b-77c3-908c-f10c14f7d040On GitHub#48080
  8. [Windows Desktop][26.917.71314] First prompt succeeds, second message cannot be sent; persists after cache cleanup and network isolationOn GitHub#48007
  9. Windows 26.915.4065.0: follow-up Send disabled or spins; voice and tool follow-ups workOn GitHub#47872
  10. Windows Codex Desktop: second message hangs indefinitely while first message worksOn GitHub#47855
Show all 38Show only the newest 10
  1. Send button becomes disabledOn GitHub#47845
  2. Can't continue prompts in one thread.On GitHub#47786
  3. [Windows desktop] Follow-up Send disabled after first turn, persists on 26.917.8451.0 (CLI works)On GitHub#47716
  4. codex send button greyed outOn GitHub#47682
  5. Windows 26.915.4065.0: Send stays disabled after the first response in every new conversationOn GitHub#47316
  6. The chat doesn't allow me to continue; after sending the first message, I'm blocked from proceeding with the conversation—the chat freezes and gets stuck loading indefinitely.On GitHub#47279
  7. Codex Desktop: fail to continue talking after the first turn in a conversationOn GitHub#47277
  8. Error continuing conversationsOn GitHub#47066
  9. Windows Codex Desktop hangs indefinitely when sending a second message in an existing taskOn GitHub#47054
  10. [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
  11. Follow up prompts fail silentlyOn GitHub#46876
  12. Windows: follow-up message submission spins indefinitely after first turn; switching chats resets spinnerOn GitHub#46824
  13. Windows: reopened chats cannot send follow-up prompts after app/system restart (26.915.4065.0)On GitHub#46814
  14. [Windows][WSL] Send button stays disabled after the first message (no turn/start is sent)On GitHub#46775
  15. Chatgpt App issue in WindowsOn GitHub#46772
  16. Send button cannot be clickedOn GitHub#46649
  17. Codex Windows: Send Button Stays Disabled After a Completed TurnOn GitHub#46619
  18. Windows Desktop: Send button disabled after first completed Local Codex/Work turn (native + WSL)On GitHub#46618
  19. macOS: Send button disabled in existing chats while voice input still worksOn GitHub#46440
  20. Windows Desktop: follow-up messages hang indefinitely after first turn; clean reinstall only fixes it temporarilyOn GitHub#46299
  21. Windows: Second message hangs indefinitely and never appears in conversation history (26.908.9136.0)On GitHub#45902
  22. [Windows Desktop][26.908.40834] Second prompt cannot be sent after first successful turn, send button becomes disabled while CLI works normallyOn GitHub#45886
  23. Unable to send chat messages in the latest version of the clientOn GitHub#45885
  24. Windows Desktop: first prompt succeeds, second message cannot be sent; reinstall only fixes it temporarilyOn GitHub#45797
  25. Windows app sends only the first message in every Codex chatOn GitHub#45775
  26. [Windows][26.908.70816] Restored / existing threads keep Send disabled; only a brand-new chat can send (CLI resume works)On GitHub#45719
  27. [Windows Desktop 26.908.70816] Follow-up messages disabled after first completed turn; existing threads cannot send (CLI unaffected)On GitHub#45626
  28. [Windows] Follow-up Send hangs during active work and after completion; prompt remains a draftOn GitHub#45404

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.