Thread name shows in `/status` but not in `/resume` list

Resolved 💬 2 comments Opened Feb 3, 2026 by taturou Closed Feb 3, 2026

What version of Codex is running?

codex-cli 0.94.0

What subscription do you have?

Team (Business)

Which model were you using?

gpt-5.2-codex

What platform is your computer?

Linux 5.15.167.4-microsoft-standard-WSL2 x86_64 x86_64

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

Windows Terminal (WSL)

What issue are you seeing?

/status shows Thread name: FooBar, but in the /resume list the same session row shows the first user message preview instead of the thread name.
Searching for FooBar in /resume does not match Session ID: 019c214e-b8f3-72c3-853c-67ba83dd735f.
${CODEX_HOME}/.codex/session_index.jsonl contains the thread name for that ID.
Example: {"id":"019c214e-b8f3-72c3-853c-67ba83dd735f","thread_name":"FooBar",...}

What steps can reproduce the bug?

  1. Start a session with CODEX_HOME=$PWD/.codex
  2. Set the thread name: /rename FooBar
  3. Confirm /status shows Thread name: FooBar
  4. Open the resume list
  5. In the CLI: /resume
  6. Or in the shell: codex resume --all
  7. The session row for ID 019c214e-b8f3-72c3-853c-67ba83dd735f shows the first user message preview instead of the thread name
  8. Searching for FooBar in /resume does not match

What is the expected behavior?

In the /resume list, the Conversation column should display the thread name FooBar for that session, and it should be searchable.

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗