Skip to content

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

Closed

Description

@corytomlinson

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

Activity

  1. github-actions commented on Mar 27, 2026

    @github-actions
    Contributor

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

    Powered by Codex Action

  2. added
    TUIIssues related to the terminal user interface: text input, menus and dialogs, and terminal display
    regressionBehaviors that worked in previous versions but were broken due to an update
    and removed
    CLIIssues related to the Codex CLI
    on Mar 27, 2026
  3. etraut-openai commented on Mar 27, 2026

    @etraut-openai
    Contributor

    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?

  4. corytomlinson commented on Mar 27, 2026

    @corytomlinson
    Author

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

    Powered by Codex Action

    Different issue.

  5. etraut-openai commented on Mar 27, 2026

    @etraut-openai
    Contributor

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

    Thanks for reporting the issue!

  6. corytomlinson commented on Mar 27, 2026

    @corytomlinson
    Author

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

  7. etraut-openai commented on Mar 28, 2026

    @etraut-openai
    Contributor

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

  8. dhruvil009 commented on May 4, 2026

    @dhruvil009

    Issue, still present in latest update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    TUIIssues related to the terminal user interface: text input, menus and dialogs, and terminal displaybugSomething isn't workingregressionBehaviors that worked in previous versions but were broken due to an update

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions