ERROR: No saved session found with ID <session_name> After Upgrade to 0.117.0

Resolved 💬 7 comments Opened Mar 27, 2026 by corytomlinson Closed Mar 28, 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?

0.117.0

What subscription do you have?

ChatGPT Enterprise

Which model were you using?

gpt-5.4

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

What issue are you seeing?

All previous saved sessions broken immediately after upgrade from 0.116.0 -> 0.117.0.
Sessions themselves are fine, but session names that were set previously using /rename are all missing from /resume. As a results codex resume <session_name> fails with error "ERROR: No saved session found with ID <session_name>. Run codex resume without an ID to choose from existing sessions."
However, the session name does still appear in the terminal tab when thread [x] is enabled in /title.
Resuming session by id still works fine.
Renaming the session again still produces error when trying to resume session by name.

What steps can reproduce the bug?

Upgrade from 0.116.0 to 0.117.0. Restart codex. Try to /resume <session_name>

What is the expected behavior?

Sessions should be resumable by name using codex resume <session_name> or /resume <session_name>

Additional information

_No response_

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 3 months ago

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

#15943

Powered by Codex Action

etraut-openai contributor · 3 months ago

It's possible this is related to the new tui_app_server feature, which was enabled by default in 0.117.0. If you disable this feature flag, does the problem go away?

corytomlinson · 3 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate. * codex resume <name> can fail after a fresh thread is auto-named, and unsaved name entries can shadow older saved sessions #15943 _Powered by Codex Action_

Different issue.

etraut-openai contributor · 3 months ago

Yes, this looks like it's related to tui_app_server. I'll work on a fix.

Thanks for reporting the issue!

corytomlinson · 3 months ago

Yes, also confirmed that launching codex --disable tui_app_server restores the functionality. Thanks for the quick response.

etraut-openai contributor · 3 months ago

Thanks for the bug report. This will be addressed in the next release.

dhruvil009 · 2 months ago

Issue, still present in latest update