Codex resume failed: recover your next steps

Check session selection and the exact failure before changing local data. Preserve the original conversation even if you continue in a new task.

Start here

Check whether the failure began right after a Codex client update, since one reported resume failure followed an update.

Preserve the conversation first

If a saved Codex conversation will not reopen, keep the original task and project files. A new task can let you continue work, but it does not repair or recover the original conversation.

SymptomNext check
Session missing from the CLI pickerCheck the working directory, Codex home and local/remote environment.
Error names paginated threads or initialTurnsPageRecord the desktop build and whether the failure began after an update.
Error includes failed to read thread or CRCPreserve the original data and report the storage read failure.
Session opens, then hits a context limitUse the stuck-session guide.

Use the documented CLI resume options

For a CLI session available in this environment, the official command reference documents:

codex resume

This opens the session picker. codex resume --last selects the most recent eligible session; codex resume --all includes sessions outside the current working directory in the picker. To choose a known session explicitly, use codex resume <SESSION_ID>, replacing the placeholder with its actual ID.

Check codex resume --help on the installation you are using if options differ. These commands reopen sessions; they are not file-repair utilities. A desktop or cloud task is not guaranteed to be accessible through a different local CLI home.

Expected result: the intended transcript opens. Check the task identity and project before sending further work.

If the failure began after a desktop update

A macOS report describes an error naming initialTurnsPage after an update. The issue being closed does not establish which version fixes it.

Save drafts, record the installed app build and try one normal relaunch. Compare another existing task without deleting either. If only one task fails, record that difference; it narrows the scope but does not prove its stored data is corrupt.

Use the same affected client when verifying recovery. A working CLI conversation is a useful comparison, not proof that the desktop task is repaired.

If the error includes CRC or a storage read failure

The reported CRC case describes unreadable session data and backups. It does not demonstrate a successful repair by moving or deleting the session store.

Preserve the originals. Before any storage investigation, save other work and make a private backup of the affected Codex data using the actual configured home. Do not rename databases, remove session directories or overwrite files with a backup as an experiment. Escalate with the exact error and affected task details; a supported recovery procedure needs to identify the damaged data first.

If you must continue, start a separate task with a concise summary from material you can still read. Check the project files and Git diff before letting the new task make changes. This is a continuity workaround, not recovery of the saved task.

Verify the result

The original conversation must reopen with its expected history and accept a new message for recovery to count as successful. If only the new task works, report the original as unresolved.

Include the app/CLI version, OS, working directory, configured home, exact error and whether other tasks open. Redact private paths and credentials. The report examples are not locally reproduced fixes, and this guide names no universal repair version.

This guide is part of our Codex sessions troubleshooting.

Compare another message in the Codex error guide library. First check whether this is a Codex service-side problem → View live Codex status.

Useful Codex tools

Sources

Each source lists what it is used to support. Sources are re-read on the review schedule, not continuously.

How this page is checked
Evidence level
Reported - based on public reports, not reproduced here
Last reviewed
2026-09-22
Content updated
2026-09-22
Full version scope
Reported on the Codex desktop app 26.715.72359 (Darwin 27.0.0) and 26.908.70816 (macOS), among others opened. No fix version can be named; the scope of the underlying cause across other versions and platforms is unknown.
Symptoms indexed
  • You closed or crashed the client and cannot reopen the conversation
  • A banner reads 'Failed to resume chat' or 'Error creating chat' naming paginated threads
  • Opening, resuming and sending messages all fail with a 'failed to read thread' store error
  • The window simply will not open or send messages after an update

Reviewer note

Source and editorial review on 2026-09-22. Official commands and documented behavior were checked against primary sources; public issue reports remain conditional evidence, not locally reproduced fixes.

Last updated: