-
Notifications
You must be signed in to change notification settings - Fork 10.7k
"codex resume" command hints print invalid <session-guid> #18011
Copy link
Copy link
Open
Labels
TUIIssues related to the terminal user interface: text input, menus and dialogs, and terminal displayIssues related to the terminal user interface: text input, menus and dialogs, and terminal displaybugSomething isn't workingSomething isn't workingregressionBehaviors that worked in previous versions but were broken due to an updateBehaviors that worked in previous versions but were broken due to an updatesessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving
Description
Metadata
Metadata
Assignees
Labels
TUIIssues related to the terminal user interface: text input, menus and dialogs, and terminal displayIssues related to the terminal user interface: text input, menus and dialogs, and terminal displaybugSomething isn't workingSomething isn't workingregressionBehaviors that worked in previous versions but were broken due to an updateBehaviors that worked in previous versions but were broken due to an updatesessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving
Type
Fields
Give feedbackNo fields configured for issues without a type.
What version of Codex CLI is running?
codex-cli 0.121.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.3-codex, gpt-5.4-codex
What platform is your computer?
Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 x86_64
What terminal emulator and version are you using (if applicable)?
wsl2
What issue are you seeing?
First observed when i upgraded from codex-cli 0.118.0 to 0.120.0 and now to 0.121.0 hoping this would already be fixed, codex-cli simply started errorneously issuing "To continue this session, run codex resume session-guid" command hints with invalid session-guids: 1) hitting ctrl+d on a new session without starting any conversation yet - this hint is issued 1x upon exiting. 2) resuming existing session, hitting ctrl+d -> two (!!) of these hints are appended to the session history with different (!!) guids. reverting to 0.118.0 doesn't do any of this.
What steps can reproduce the bug?
Empty session:
Existing session:
What is the expected behavior?
Expected behaviour is not to print "codex resume" command hint with invalid session guid which can't be resumed (on both empty + existing session).
Additional information
No response