Follow-up messages cannot be sent

“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/issues/15541/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 31 a week at the late-September peak. A workaround is known.

Follow-up messages cannot be sent after the first turn. After the first response finishes, the Send button stays disabled or spins indefinitely and typed text remains in the composer.

Is this your bug?

File my report

Where: Windows desktop app
Versions: 0.154.0 to 26.917.71314
Platforms: Windows
How bad: Breaks a normal workflow. Some reports say it blocks them completely.

Part of: Follow-up messages won't send4 bugs

Second message hangs indefinitely7 people
Send button stays disabled in reopened existing chats6 people
Follow-up Send hangs3 people

Original reports23, newest first

Oct 29, 2026Codex Windows App – Follow-up messages get stuck on sending and are never submittedOn GitHub#58039
Sep 25, 2026[Windows] Cannot submit a second message in Codex after the first turn completesOn GitHub#48180
Sep 25, 2026[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
Sep 25, 2026[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
Sep 25, 2026no-active-thread-01a0d896-a90b-77c3-908c-f10c14f7d040On GitHub#48080
Sep 25, 2026[Windows Desktop][26.917.71314] First prompt succeeds, second message cannot be sent; persists after cache cleanup and network isolationOn GitHub#48007
Sep 24, 2026Send button becomes disabledOn GitHub#47845
Sep 24, 2026Can't continue prompts in one thread.On GitHub#47786
Sep 23, 2026[Windows desktop] Follow-up Send disabled after first turn, persists on 26.917.8451.0 (CLI works)On GitHub#47716
Sep 23, 2026codex send button greyed outOn GitHub#47682

Show all 23Show only the newest 10

Sep 22, 2026Windows 26.915.4065.0: Send stays disabled after the first response in every new conversationOn GitHub#47316
Sep 22, 2026Codex Desktop: fail to continue talking after the first turn in a conversationOn GitHub#47277
Sep 21, 2026Error continuing conversationsOn GitHub#47066
Sep 20, 2026[Windows][WSL] Send button stays disabled after the first message (no turn/start is sent)On GitHub#46775
Sep 20, 2026Chatgpt App issue in WindowsOn GitHub#46772
Sep 19, 2026Send button cannot be clickedOn GitHub#46649
Sep 19, 2026Codex Windows: Send Button Stays Disabled After a Completed TurnOn GitHub#46619
Sep 19, 2026Windows Desktop: Send button disabled after first completed Local Codex/Work turn (native + WSL)On GitHub#46618
Sep 17, 2026Windows Desktop: follow-up messages hang indefinitely after first turn; clean reinstall only fixes it temporarilyOn GitHub#46299
Sep 16, 2026[Windows Desktop][26.908.40834] Second prompt cannot be sent after first successful turn, send button becomes disabled while CLI works normallyOn GitHub#45886
Sep 15, 2026Windows Desktop: first prompt succeeds, second message cannot be sent; reinstall only fixes it temporarilyOn GitHub#45797
Sep 15, 2026Windows app sends only the first message in every Codex chatOn GitHub#45775
Sep 15, 2026[Windows Desktop 26.908.70816] Follow-up messages disabled after first completed turn; existing threads cannot send (CLI unaffected)On GitHub#45626