›_ Codex Issues
Codex Issues / #16562

codex resume --all still shows initial prompt instead of stored session name on 0.118.0

Resolved 💬 3 comments Opened Apr 2, 2026 by IgRoF Closed Apr 2, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.118.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.4

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

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

Windows Terminal (WSL and PowerShell)

What issue are you seeing?

On 0.118.0, direct resume by stored session name works again, but codex resume --all still shows the initial prompt preview in the Conversation column instead of the stored human-readable session name.

So the naming metadata exists and is usable for resume-by-name, but the picker display still falls back to the first prompt.

What steps can reproduce the bug?

  1. Rename a session with /rename SOME_NAME.
  2. Exit the session.
  3. Run: codex resume --all
  4. The picker still shows the initial prompt / conversation preview instead of SOME_NAME.

What is the expected behavior?

If thread_name exists, the picker should display that instead of the initial prompt preview.

Additional information

In my local testing:

  • thread_name in ~/.codex/session_index.jsonl exists
  • direct codex resume "<thread_name>" works on 0.118.0
  • but the picker still shows the initial prompt preview

Workaround I used locally:

  • keep the real session name in session_index.jsonl
  • also prefix threads.first_user_message in ~/.codex/state_5.sqlite with [Human-readable name] ...
  • then codex resume --all shows the readable label again

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #16405
  • #16280

Powered by Codex Action

IgRoF · 4 months ago
Potential duplicates detected. Please review them and close your issue if it is a duplicate. * Thread rename updates session_index but leaves SQLite thread title stale #16405

Not a duplicate: #16405 is about rename metadata drifting between session_index.jsonl and SQLite threads.title, while my bug is that codex resume --all still shows the initial prompt even when thread_name already exists and codex resume "<thread_name>" works on 0.118.0.

EDIT: @etraut-openai On closer read, this bug is probably related to #16405. Fixing #16405 might fix this bug too, so feel free to close this bug if that's the case.

* Resume picker and name-based resume appear to use session_index.jsonl thread_name, not state_5.sqlite title #16280

This was my original bug describing the same issue, but it also contained the now-fixed codex resume "<thread_name>" issue, so the bug was closed. This bug refers only to the still-unfixed codex resume --all issue.

etraut-openai contributor · 4 months ago

Thanks for the bug report. Tis will be fixed in the next release.