Active-writer resume not retried

“After relaunch, opening the original chat fails with JSON-RPC -32600 / already has an active writer and presents a fork path.”

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

Resume fails on transient active-writer conflict without retrying. Resume fails with JSON-RPC -32600 "already has an active writer"; follow-ups stay queued and a fork path is offered, though the original chat later resumes.

Is this your bug?

File my report

Where: Desktop app resume
Error text: thread <redacted> already has an active writer
Versions: 26.1023.51421
Platforms: macOS
How bad: Breaks a normal workflow.

Part of: Conversation writer lock blocks continuing5 bugs

Active writer conflict4 people
Conversation locked by another app11 people
Mobile conversation stays locked5 people
Conversation locked after exit5 people

Not quite your bug?

Threads fail to resume4 people

Original reports2, newest first

Oct 29, 2026[macOS Desktop 26.1023] Follow-ups stay paused after transient thread writer conflict; resume helper does not retryOn GitHub#58055
Oct 24, 2026[macOS Desktop] Transient active-writer conflict stops resume retries and offers fork despite original recovering seconds laterOn GitHub#56751