codex resume <renamed-session>` fails after renaming session

Resolved 💬 1 comment Opened Mar 28, 2026 by hezhexi2002 Closed Mar 28, 2026

What version of Codex CLI is running?

codex-cli 0.117.0

What subscription do you have?

Business

Which model were you using?

gpt-5.4 (xhigh reasoning effort)

What platform is your computer?

Linux (CentOS 7, kernel 3.10.0-957.el7.x86_64)

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

zsh

What issue are you seeing?

After renaming a session, codex resume <new-name> fails with "No saved session found with ID <new-name>".

The rename command itself suggests the new name should work:
"Thread renamed to planb, to resume this thread run codex resume planb"

However, running codex resume planb returns:
"ERROR: No saved session found with ID planb"

The session can only be resumed via the interactive menu or using the full session ID.

What steps can reproduce the bug?

Uploaded thread: 019d3245-c430-7a12-afa5-1cfe30e886dc

  1. Start a codex session
  2. Rename the session by typing: rename planb
  3. Exit the session
  4. Run: codex resume planb
  5. Error appears: "ERROR: No saved session found with ID planb"

What is the expected behavior?

codex resume planb should successfully resume the renamed session, as suggested by the rename confirmation message.

Additional information

Uploaded thread: 019d3245-c430-7a12-afa5-1cfe30e886dc

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗