Its theme's rank, 14 days: 27 on the Codex sheet
5 people reported

All time, since Oct 16, including 3 thumbs-up on GitHub.

Conversation locked after exit

“The only recovery choices shown were Retry and Fork chat.”

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

Finished conversation stays locked as open in another app. Resuming an existing conversation shows an "open in another app" block after the CLI exits or when using --no-daemon, offering only Retry and Fork chat.

Is this your bug?

File my report
Where
Conversation resume
Versions
0.163.0 to 0.164.0
Platforms
macOS
How bad
Breaks a normal workflow.

Part of: Conversation writer lock blocks continuing5 bugs

  1. Active writer conflict4 people
  2. Conversation locked by another app11 people
  3. Mobile conversation stays locked5 people
  4. Active-writer resume not retried2 people

Original reports2, newest first

  1. [macOS][0.164.0] Completed CLI thread stays locked in Desktop after exit; agents Stop offers no handoffOn GitHub#57004
  2. [0.163.0][WSL2] Idle daemon locks block --no-daemon recovery; misleading "another app" error and no "Switch here"On GitHub#54738

Do you work on Codex?

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