# Codex session recovery checklist

An original, reusable note template from CodexAnywhere.
Guide: https://codexanywhere.app/blog/codex-resume-session#recovery-checklist
Reviewed: October 10, 2026.

Fill this in locally. This file does not run commands, import sessions, or send
information to CodexAnywhere. Keep the completed note private when it contains
project paths, session identifiers, code details or provider receipts. Do not
include passwords, API keys, authentication files, private code or full transcripts.

## 1. Identify the work

- Execution host (this computer, connected remote host, or cloud):
- Intended saved session (record locally):
- Repository and intended working directory:
- Branch and commit:
- Uncommitted or untracked changes that must be preserved:
- Local-only dependencies or services required to continue:

## 2. Inspect before resuming

Run only inside the intended Git checkout. These are read-only inspection commands:

```sh
codex --version
codex resume --help
git rev-parse --show-toplevel
git branch --show-current
git rev-parse --short HEAD
git status --short
git diff --stat
```

Check the original surface for the saved conversation and active process state.
Git does not store the Codex transcript or an active process. `git status --short`
shows ordinary untracked files but does not list ignored files. Inspect required
local-only files separately without copying secrets into Git or shared notes.

## 3. Record the last result

- Last requested action:
- Result: verified success / verified failure / unknown
- Evidence (test output, provider receipt, commit, or application state):
- Outstanding approval or missing input:
- One next step:

For external side effects, inspect the receiving system before retrying.
A missing final chat reply does not prove a deployment, migration or submission
failed. If the result remains unknown, obtain evidence before repeating the action.
Do not convert an unknown result into a successful result to complete this note.

## 4. Continue the intended session

Use the installed CLI help before choosing a command. `codex resume` opens the
interactive picker. `codex resume --last` selects the latest session within the
current working directory according to the official reference; `--all` expands
directory scope. Prefer an explicit session ID when multiple runs overlap.
These options do not import sessions or move project files from another machine.

Example continuation prompt (adapt before sending):

> Resume this task by inspecting the intended session, execution host, working
> directory, branch, changed files and last verified result. First summarize what
> is complete, what is uncertain and one next step. Before repeating any external
> action, check its receipt or current application state. Do not edit files or
> retry that action until the inspection establishes what remains.

## Sources and limits

- Official resume reference: https://learn.chatgpt.com/docs/developer-commands#codex-resume
- CodexAnywhere handoff guide: https://codexanywhere.app/codex-session-sync
- Local version/help observed: Codex CLI 0.160.0, October 10, 2026.
- No cross-device import or resumed execution was tested for this checklist.
- CodexAnywhere is independent and not affiliated with OpenAI. Its own session-sync
  service remains a concept in development and is not available to use.

The original checklist prose may be copied, adapted and shared with attribution
and a link to the guide. Do not redistribute a completed private note by mistake.
