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
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?
- Rename a session with
/rename SOME_NAME. - Exit the session.
- Run:
codex resume --all - 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
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗