Session ID not saving
Resolved 💬 4 comments Opened Feb 5, 2026 by Redstar1337 Closed Mar 16, 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.97
What subscription do you have?
Pro
Which model were you using?
GPT 5.2
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What terminal emulator and version are you using (if applicable)?
PS7
What issue are you seeing?
Quitting a session says to to resume type resume "ID name I gave it" but doing that doesnt work says ID not found, it only worked in the early version when it released (I think 94)
What steps can reproduce the bug?
Mentioned above, codex --dangerously-bypass-approvals-and-sandbox -s danger-full-access resume 'ID' doesn't work even though it tells me exactly what to type to resume. Using the normal resume and picking the convo then re-exiting resets it back to session ID not name.
What is the expected behavior?
_No response_
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I'm not able to repro the problem. Is there something special or unusual about the name you're choosing? I've tried names with spaces, names with non-ASCII unicode characters, etc.
If the name contains spaces, you'll need to use quotes around the name.
I think I figured it out, it works now after the update of 0.97, but I only close out sessions when a new update comes out to restart the session, that's when that happens.
I guess it's an issue when you make a CLI update, you need to rename them again. In my specific case, I updated the CLI package while the sessions were still open (older version), restarting that session to launch the newer version produced that error.
Ah, thanks for the clarification. This might have been a bug in the previous version where it wasn't correctly persisting the name. If you see the problem again (like when you upgrade from 0.97 to 0.98), let us know.