Codex RescueCodex troubleshooting

Codex stuck sessions & resume errors

Troubleshoot stuck Codex turns, stalled sessions and resume failures. Check session state and recovery options before starting over or removing data.

When Codex appears stuck, preserve the useful work before trying recovery steps. A stalled turn and a session that cannot resume are different problems; choose the guide that matches what you can still see and control.

A session can be slow, waiting for a tool, stuck in one turn or unable to resume an earlier chat. Those are not identical failures. Record the last visible action, whether there is new output, and whether you can still access the current conversation. Preserve useful work before testing recovery: a new chat may be a helpful comparison, but it should not replace the only copy of a task or local project state. Check public status when several clients fail at the same time, while keeping local symptoms in view.

The guides below distinguish a stalled current turn from a resume failure and related session messages. Use the one that matches what you can actually observe. Avoid deleting session files or the entire Codex home as a generic reset. If the current task remains accessible, keep it while gathering a redacted error line, client version, operating system and time of failure. That evidence is more useful than a broad “stuck” label when deciding whether to wait, retry a specific action or report a reproducible bug.

What to check first

  • Save relevant output and note the last completed action.
  • Determine whether the current turn is stalled or an old session will not reopen.
  • Use targeted recovery steps before deleting local session files.

Sessions troubleshooting guides

Back to all Codex error messages →

Reached a usage limit instead? Check Codex usage limits and reset times.

Last updated: