Follow-up prompts stuck or lost

“The Codex VS Code extension on Windows can leave follow-up messages indefinitely stuck in Queue after the previous response has completed.”

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/9145/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

Quiet. No reports and thumbs-up in the last two weeks, down from 140 a week at the late-September peak. A workaround is known.

Follow-up prompts disappear or stay stuck in queue. In the VS Code extension, submitted prompts vanish from the composer or stay queued after a completed turn; earlier messages may replay.

Is this your bug?

File my report

Where: VS Code extension
Error text: Failed to release queued message send lock
errorMessage="\"undefined\" is not valid JSON"Pasted in 7 reports
errorName=SyntaxErrorPasted in 6 reports
[error] [desktop-notifications][global-error] ResizeObserver loop completed with undelivered notifications.Pasted in 2 reports
Versions: 0.118.0 to 26.5928.31416
Platforms: Linux, macOS, Windows
How bad: Breaks a normal workflow. Some reports say it used to work.

Part of: VS Code follow-ups stuck in queue4 bugs

Not quite your bug?

Follow-up prompts stay queued5 people

Original reports39, newest first

Oct 4, 2026Codex VS Code queue fix: disappearing messages, stuck sending and duplicate prompts — tests and four patchesOn GitHub Discussions#50980
Oct 4, 2026Codex VS Code extension is acting up - the chat eats up prompts silentlyOn the forum#1403271
Oct 3, 2026VS Code Codex regression: follow-up prompts disappear after submission in 26.930.31730; downgrading to 26.917.62051 fixes itOn GitHub#50746
Oct 3, 2026VS Code Codex messages intermittently stuck before turn creation after extension updateOn GitHub#50742
Oct 3, 2026Follow-up messages get stuck in queue and only send after restarting VS CodeOn GitHub#50736
Oct 3, 2026Codex VS Code extension: prompts intermittently disappear after Send or remain stuck in queueOn GitHub#50733
Oct 3, 2026VS Code Codex extension intermittently hangs/buffers and loses queued turn state on Windows 10On GitHub#50713
Oct 3, 2026Follow-up prompts remain pending after the first completed task in VS CodeOn GitHub#50692
Oct 3, 2026VS Code: Follow-up stuck in Queue after completed turn, send-lock release fails and previous turn replaysOn GitHub#50683
Oct 3, 2026[VS Code / WSL2] Prompts disappear after Enter or Send without being processedOn GitHub#50655

Show all 39Show only the newest 10

Oct 3, 2026Codex VS Code extension: submitted prompts get stuck, disappear, or remain as pendingOn GitHub#50653
Oct 3, 2026VS Code follow-up messages disappear or remain queued until restart on WindowsOn GitHub#50609
Oct 2, 2026Bug - Codex VS Code Ext - prompts are not queued or load forever - with solutionOn the forum#1403015
Oct 2, 2026VS Code: completed turns remain markedStreaming=true, causing follow-up prompts to get stuck in queue or disappearOn GitHub#50486
Oct 2, 2026VS Code extension: queued messages silently fail to send — "Failed to release queued message send lock" (SyntaxError: "undefined" is not valid JSON)On GitHub#50403
Oct 2, 2026[VS Code Remote SSH] Intermittent dropped/stalled prompts on headless Debian Trixie with 26.928.31416; send-lock JSON parse errorsOn GitHub#50394
Oct 2, 2026VS Code extension: sent follow-up stays "processing" forever and gets re-sent (regression in 26.928.31416 / 26.5928.31416)On GitHub#50368
Oct 2, 2026VS Code extension: sent follow-up stays "processing" forever and gets re-sent (regression in 26.928.31416 / 26.5928.31416)On GitHub#50365
Oct 2, 2026Codex VS Code extension on Linux silently drops submitted follow-up prompts.On GitHub#50363
Oct 2, 2026[Windows][VS Code extension] Multi-turn Codex sessions stop responding after first prompt in recent extension versionsOn GitHub#50361
Oct 2, 2026VS Code Codex messages frequently spin for minutes; queue-lock JSON errorsOn GitHub#50351
Oct 2, 2026Codex extension bug: prompt disappears in existing thread without runningOn GitHub#50295
Oct 2, 2026VS Code extension loses prompts and queues new prompts foreverOn GitHub#50249
Oct 2, 2026Messages get stuck in queue or disappear after 2–3 turns in VS CodeOn GitHub#50239
Oct 2, 2026[VS Code] Submitted messages intermittently disappear / are lost, and extension issue reporting is unavailableOn GitHub#50225
Oct 2, 2026Codex VS Code bug: queued follow-up messages remain stuck after previous task finishesOn GitHub#50187
Oct 2, 2026Messages stuckOn GitHub#50175
Oct 1, 2026Queuing a prompt does not workOn GitHub#50124
Oct 1, 2026VS Code Codex queues prompts after completed turn; thread remains markedStreaming=trueOn GitHub#50118
Oct 1, 2026VS Code: delivered message remains pending locally and replays with the same clientId after reloadOn GitHub#50107
Oct 1, 2026VS Code Codex extension remains stuck in streaming state after turn completes; restarting Extension Host fixes itOn GitHub#50084
Oct 1, 2026Chat on VsCode Codex Plugin does not work - major blocker - today's update bugOn GitHub#50080
Oct 1, 2026Codex VS Code 26.928.31416 repeatedly stalls: queued-message lock release fails with "undefined" is not valid JSONOn GitHub#50047
Oct 1, 2026Codex IDE plugin silently eats messagesOn the forum#1402586
Oct 1, 2026VS Code Codex 26.928.31416: normal messages disappear, spin forever, or get stuck in steer-like pending stateOn GitHub#49991
Oct 1, 2026Code extension intermittently drops submitted messages after update.On GitHub#49988
Oct 1, 2026Messages get stuck in send queue — "undefined" is not valid JSON on queued message lock releaseOn GitHub#49975
Oct 1, 2026VS Code: follow-up message stays pending after the previous response finishesOn GitHub#49955
Oct 1, 2026VS Code: follow-up messages stuck sending in Codex extension 26.928.31416On GitHub#49854