codex - 💡(How to fix) Fix codex resume --all does not list existing local sessions, while resume <session-id> can open them [1 comments, 2 participants]

What version of Codex CLI is running?

0.125.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.4-mini, gpt-5.4, gpt-5.4, gpt-5.5, etc

What platform is your computer?

Darwin 25.4.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Terminal.app and VSCode integrated terminal

What issue are you seeing?

Existing local sessions still exist under ~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl.

However:

codex resume --all

shows "No sessions yet".

Direct resume by session id works:

codex resume <session-id>

Example:

codex resume 019dd81b-cdcd-7da1-8b5a-ee131f2f004a

This suggests the local session files still exist and are readable, but the session picker/index is stale, corrupted, or not rebuilt.

The issue started after switching authentication/config from API key custom provider to ChatGPT account login.

The same local-state issue also appears to affect the VSCode Codex extension because it uses the same ~/.codex directory.

What steps can reproduce the bug?

1. Use Codex CLI with existing local sessions stored in ~/.codex/sessions.

2. Confirm rollout files exist, for example:

~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl

1. Change authentication/configuration (in my case: switched from API key custom provider to ChatGPT login).

2. Run:

codex resume --all

1. Observe the picker shows "No sessions yet".

2. Run:

codex resume <existing-session-id>

1. Observe the session can still be opened or partially resumed.

Expected: resume --all should list all valid local sessions.

Actual: resume --all shows no sessions even though valid local sessions exist.

What is the expected behavior?

codex resume --all should detect and list all valid local sessions stored under ~/.codex/sessions.

If local index files are stale or missing, Codex should automatically rebuild the session picker from existing rollout session files.

Sessions that can be opened with:

codex resume <session-id>

should also appear in the resume --all picker.

The VSCode extension should show the same local sessions when it uses the same ~/.codex state directory.

Additional information

Relevant local files existed during the issue:

~/.codex/sessions/**/*.jsonl ~/.codex/history.jsonl ~/.codex/session_index.jsonl ~/.codex/state_5.sqlite ~/.codex/logs_2.sqlite

The problem began after switching authentication/configuration from API key custom provider to ChatGPT login.

Direct resume by session id still works, which suggests the sessions themselves are not lost.

This looks like a local session index / picker synchronization problem rather than missing session data.