Support dump and resume conversations
Resolved 💬 8 comments Opened Aug 11, 2025 by ethe Closed Oct 19, 2025
💡 Likely answer: A maintainer (tibo-openai, collaborator)
responded on this thread — see the highlighted reply below.
Codex CLI currently does not support dumping a conversation to a folder and resuming it. It would be better if we can support persisting conversations, and resume them later. It is really useful to enhance the user experience.
8 Comments
no session restoration is totally a joke for a CLI. Can't believe the Codex team didn't implement this feature in the first place.
My machine just crashed when in the middle of a complicated codex session. It would be very useful if I could just resume where I was. Claude code already has a
/resumecommand for this.Coming from Claude Code, this is a must have feature.
Upvote for this.
0.30.0added the start of support for--resumeand--continue:See also:
In claude code, --resume and --continue work per-folder. It appears this is global. Is there a reason for that? Is there a way to adjust that to instead be per-folder?
I had a session started on codex 0.25 that stopped working today, probably because the model it was using has been retired while I was working. I tried upgrading to the latest codex and resuming that session, but it doesn't show any of my previous sessions from 0.25, I get "No sessions found" when I use --resume.
Later edit: looking at the session files, it seems the JSON changed significantly between 0.25 and 0.35, that's probably why it doesn't recognize the old sessions. Hopefully such format changes won't happen frequently.
This is now supported with
codex resume.