161 people reported

All time, since Oct 1, including 116 thumbs-up on GitHub.

VS Code follow-ups stuck in queue

“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/themes/110/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 160 a week at the late-September peak.

4 bugs in this theme

  1. Follow-up prompts stuck or lostHas a workaround140 people
  2. Prompts stuck on spinnerHas a workaround11 people
  3. Follow-up prompts hangHas a workaround8 people
  4. Composer stops sending promptsNo workaround yet3 people

What's included

  • Follow-up prompt sits in the pending area with a spinner after the previous response finished; only a restart or reload clears it
  • Submitted prompt disappears from the composer without reaching the conversation or queue
  • Earlier completed message is sent and answered again after cancelling or restarting
  • Log shows "Failed to release queued message send lock" with "undefined" is not valid JSON
  • "Active writer" conflict when the same chat is open in more than one window; composer stops sending or shows "Delivery could not be confirmed"

Not included

  • Dictation failing with a 403 Cloudflare challenge
  • Feedback submission failing with "couldn't verify feedback permissions"
  • First prompt in a new chat never getting a response

Original reports47, newest first

  1. Codex VS Code queue fix: disappearing messages, stuck sending and duplicate prompts — tests and four patchesOn GitHub Discussions#50980
  2. Codex VS Code extension is acting up - the chat eats up prompts silentlyOn the forum#1403271
  3. VS Code Codex regression: follow-up prompts disappear after submission in 26.930.31730; downgrading to 26.917.62051 fixes itOn GitHub#50746
  4. VS Code Codex messages intermittently stuck before turn creation after extension updateOn GitHub#50742
  5. Follow-up messages get stuck in queue and only send after restarting VS CodeOn GitHub#50736
  6. Codex VS Code extension: prompts intermittently disappear after Send or remain stuck in queueOn GitHub#50733
  7. VS Code Codex extension intermittently hangs/buffers and loses queued turn state on Windows 10On GitHub#50713
  8. Follow-up prompts remain pending after the first completed task in VS CodeOn GitHub#50692
  9. VS Code: Follow-up stuck in Queue after completed turn, send-lock release fails and previous turn replaysOn GitHub#50683
  10. [VS Code / WSL2] Prompts disappear after Enter or Send without being processedOn GitHub#50655
Show all 47Show only the newest 10
  1. Codex VS Code extension: submitted prompts get stuck, disappear, or remain as pendingOn GitHub#50653
  2. VS Code follow-up messages disappear or remain queued until restart on WindowsOn GitHub#50609
  3. Bug - Codex VS Code Ext - prompts are not queued or load forever - with solutionOn the forum#1403015
  4. VS Code: completed turns remain markedStreaming=true, causing follow-up prompts to get stuck in queue or disappearOn GitHub#50486
  5. Codex VS Code extension (openai.chatgpt) on Windows: Chat stalls after first reply + dictation fails (403 cloudflare_challenge)On GitHub#50430
  6. Codex in VS Code stalls / “Thinking” indefinitely; messages replay; Failed to release queued message send lock + undefined is not valid JSON ** Repair **On GitHub#50404
  7. VS Code extension: queued messages silently fail to send — "Failed to release queued message send lock" (SyntaxError: "undefined" is not valid JSON)On GitHub#50403
  8. [VS Code Remote SSH] Intermittent dropped/stalled prompts on headless Debian Trixie with 26.928.31416; send-lock JSON parse errorsOn GitHub#50394
  9. VS Code extension: sent follow-up stays "processing" forever and gets re-sent (regression in 26.928.31416 / 26.5928.31416)On GitHub#50368
  10. VS Code extension: sent follow-up stays "processing" forever and gets re-sent (regression in 26.928.31416 / 26.5928.31416)On GitHub#50365
  11. Codex VS Code extension on Linux silently drops submitted follow-up prompts.On GitHub#50363
  12. [Windows][VS Code extension] Multi-turn Codex sessions stop responding after first prompt in recent extension versionsOn GitHub#50361
  13. VS Code Codex messages frequently spin for minutes; queue-lock JSON errorsOn GitHub#50351
  14. VS Code composer silently stops sending after “active writer” conflictOn GitHub#50330
  15. Codex VS Code extension hangs on next prompt after previous response completesOn GitHub#50305
  16. Windows VS Code / Codex 26.930.21537. Endless loading when sending follow-up questions and steering. Reload Window briefly restores normal behavior, but it recurs. Logs repeatedly show Failed to release queued message send lock, "undefined" is not valid JSON.On GitHub#50297
  17. Codex extension bug: prompt disappears in existing thread without runningOn GitHub#50295
  18. [IDE Extension] New chats fail after 1–2 turns with active writer conflict and broken send lockOn GitHub#50269
  19. VS Code extension loses prompts and queues new prompts foreverOn GitHub#50249
  20. Messages get stuck in queue or disappear after 2–3 turns in VS CodeOn GitHub#50239
  21. [VS Code] Submitted messages intermittently disappear / are lost, and extension issue reporting is unavailableOn GitHub#50225
  22. Codex VS Code bug: queued follow-up messages remain stuck after previous task finishesOn GitHub#50187
  23. Messages stuckOn GitHub#50175
  24. Queuing a prompt does not workOn GitHub#50124
  25. VS Code Codex queues prompts after completed turn; thread remains markedStreaming=trueOn GitHub#50118
  26. VS Code: delivered message remains pending locally and replays with the same clientId after reloadOn GitHub#50107
  27. VS Code Codex extension remains stuck in streaming state after turn completes; restarting Extension Host fixes itOn GitHub#50084
  28. Chat on VsCode Codex Plugin does not work - major blocker - today's update bugOn GitHub#50080
  29. Codex VS Code 26.928.31416 repeatedly stalls: queued-message lock release fails with "undefined" is not valid JSONOn GitHub#50047
  30. Codex IDE plugin silently eats messagesOn the forum#1402586
  31. VS Code Codex 26.928.31416: normal messages disappear, spin forever, or get stuck in steer-like pending stateOn GitHub#49991
  32. Code extension intermittently drops submitted messages after update.On GitHub#49988
  33. Messages get stuck in send queue — "undefined" is not valid JSON on queued message lock releaseOn GitHub#49975
  34. VS Code: follow-up message stays pending after the previous response finishesOn GitHub#49955
  35. VS Code Codex extension 26.928.31416 gets stuck on spinner after several prompts; 403 Cloudflare challenge in Codex.logOn GitHub#49949
  36. Codex VS Code extension gets stuck after a few messages; logs show Cloudflare 403 + queued message send lock failureOn GitHub#49943
  37. VS Code: follow-up messages stuck sending in Codex extension 26.928.31416On GitHub#49854

Do you work on Codex?

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