3 people reported

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

Composer stops sending prompts

“Messages disappear after pressing Enter, later return to the composer, or appear as Steering although no agent turn is running.”

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

Composer stops sending after active writer thread conflict. In the VS Code extension, follow-up prompts stay in the composer or show "Delivery could not be confirmed" after a few turns.

Is this your bug?

File my report
Where
VS Code extension
Error text
thread-store conflict: thread <REDACTED> already has an active writer
Versions
26.5928.31416
Platforms
Linux, macOS

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

  1. Follow-up prompts stuck or lost140 people
  2. Follow-up prompts hang8 people
  3. Prompts stuck on spinner11 people

Not quite your bug?

  1. Stale "open in another app" lock2 people

Original reports2, newest first

  1. VS Code composer silently stops sending after “active writer” conflictOn GitHub#50330
  2. [IDE Extension] New chats fail after 1–2 turns with active writer conflict and broken send lockOn GitHub#50269

Do you work on Codex?

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