Active writer conflict

“thread-store conflict: thread <redacted> already has an active writer”

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

Still happening. 1 report or thumbs-up in each of the last two weeks. A workaround is known.

Thread blocked by active writer conflict across remote and desktop clients. Sending to or opening an existing thread fails with "already has an active writer" or "This is open in another app"; Retry does not help.

Is this your bug?

File my report

Where: Remote Control
Error text: thread-store conflict: thread <redacted> already has an active writer
Versions: 15.7.9 to 26.1007.21159
Platforms: macOS, Windows
How bad: Breaks a normal workflow.

Part of: Conversation writer lock blocks continuing5 bugs

Conversation locked by another app11 people
Mobile conversation stays locked5 people
Conversation locked after exit5 people
Active-writer resume not retried2 people

Not quite your bug?

Desktop requests expire queued after RPC stalls fill in-flight slots4 people

Original reports3, newest first

Oct 25, 2026[Remote][macOS → Windows] Paired client can read chats but cannot continue them: “open in another app” / active writer conflictOn GitHub#56936
Oct 24, 2026[Windows][Desktop Remote SSH] Disconnect leaves conversation writer owned by managed daemon; local Desktop unblocks only after codex app-server daemon stopOn GitHub#56797
Oct 9, 2026[macOS] SSH-started app-server competes with Desktop Remote Control, causing persistent active-writer conflicts for an idle threadOn GitHub#52675