Repository navigation
Support dump and resume conversations #2173
Description
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.
Activity
vdp641 commentedon Aug 20, 2025
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.
hakonhagland commentedon Aug 28, 2025
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.onerok commentedon Aug 29, 2025
Coming from Claude Code, this is a must have feature.
mtrin commentedon Sep 1, 2025
Upvote for this.
0xdevalias commentedon Sep 7, 2025
0.30.0added the start of support for--resumeand--continue:See also:
jcherniak commentedon Sep 8, 2025
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?
vnicolici commentedon Sep 12, 2025
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.
tibo-openai commentedon Oct 19, 2025
This is now supported with
codex resume.