Its theme's rank, 14 days: 27 on the Codex sheet
11 people reported
All time, since Sep 17, including 8 thumbs-up on GitHub.
Conversation locked by another app
“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/16148/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
Resumed conversation blocked by "open in another app" lock. Opening the same thread in another window, machine, reconnected VS Code host, or after a fork shows the lock with no handoff.
Is this your bug?
File my report- Where
- conversation resume
- Error text
thread-store conflict: thread <redacted> already has an active writer- Versions
- 0.154.0 to 0.155.1
- Platforms
- Linux
- How bad
- Breaks a normal workflow. Some reports say it used to work.
Part of: Conversation writer lock blocks continuing5 bugs
- Active writer conflict4 people
- Mobile conversation stays locked5 people
- Conversation locked after exit5 people
- Active-writer resume not retried2 people
Not quite your bug?
- Stale "open in another app" lock2 people
Original reports3, newest first
- [VS Code Remote SSH] Reconnect hides a live thread behind 'another app' lock with no read-only history or handoffOn GitHub#46936
- Regression: resumed conversations are single-writer locked across windows and machinesOn GitHub#46652
- Fork won't release the lock on the original conversationOn GitHub#46355