Threads fail to resume

“Existing Codex desktop chats fail to resume with no rollout found for thread id <id>.”

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

Quiet. No reports in the last two weeks, down from 3 a week at the early-October peak.

Threads fail to resume with no rollout found error. Opening affected chats shows "Failed to resume chat"; deleting or archiving them also fails with the missing-rollout error.

Is this your bug?

File my report

Where: thread resume
Error text: no rollout found for thread id
Versions: 0.160.1 to 26.1007.30912
Platforms: macOS
How bad: Breaks a normal workflow. Some reports say it blocks them completely.

Part of: Desktop chat list out of sync3 bugs

Denied thread reads retry endlessly5 people
Cloud tasks missing from sidebar12 people

Not quite your bug?

Tasks stuck on Starting your task113 people
Chats fail to open2 people

Original reports4, newest first

Oct 11, 2026[macOS Desktop 26.1007] Blank ghost chats keep appearing and fail to resume with missing rolloutOn GitHub#53209
Oct 9, 2026Desktop: existing chats cannot resume or delete with no rollout found; placement format version 3 errorOn GitHub#52613
Oct 8, 2026[macOS][Desktop][Dot] Chat fails to resume after normal useOn GitHub#52218
Oct 7, 2026CLI: after deleting an agent, new threads queue prompts and fail to resumeOn GitHub#51753