Resuming a previous session

[marcoscale98]

How can I resume a previous session made in a repository in auto-mode? Resuming the latest chat and memory
I run codex --history but I'm not be able to resume an history

[izuku-franck1555]

After typing codex --history, press the "Tab" key to switch to the option for resuming a conversation.

[varenc]

The --history flag seems to have been removed in a recent update. Very unclear to me what the alternative is now.

[aa755]

doesnt really work, especially if the to-be-resumed conversation is long (gets clipped?). I asked it to summarize the resumed conversation and the summary was useless. It would be great if there was a way to resume as if the process had never stopped. to "suspend", codex should dump the current state to disk and resume should reload it.

[aa755]

it seems codex --history no nonger works. but the history of past sessions can still be found in ~/.codex/session on linux (arch).

[mrqs001]

But can it be used?

[matssk]

Kinda. It's not built it, but you can ask codex to use regular cli tools to read and parse the files.

[milisp]

👉from 0.36.0

codex resume

✅ from 0.30.0

codex --resume

I built a powerful IDE/GUI for Codex CLI. Check it out

• https://github.com/milisp/codexia

I think codex should organize sessions by projects like Claude code ~/.codex/projects/{project_realpath}/{session_id}.

[reconrad48]

I think codex should organize sessions by projects like Claude code ~/.codex/projects/{project_realpath}/{session_id}.

codex -r will be better

I also built Codexia VSCode (with chat UI) & Tauri GUI version. Check it out

• https://github.com/milisp/codexia-vscode
• https://github.com/milisp/codexia - Tauri GUI with FileTree & notepad
  Feedback welcome!

Wouldn't be a bad solution except I use Codex Cli inside of VS Code the login authentication so I don't have to use a seperate API.

[milisp]

Don't need OpenAI API, you can use Codex cli login ChatGPT first, only other providers need api key

[miguelang611]

Resuming sessions is a very handy thing. Can't really switch from Claude if I am not able to resume sessions.

For example, if you make a MCP change, you need to restart Codex. If resuming is not possible, it pretty much kills it.

Also, sometimes you may leave a task half done and just wanna resume it the day after or after the weekend... It is a pity not being able to check the history and resuming!

[am-will]

if OAI actually cares about developers they'll prioritize this one for sure.

[zhefciad]

Please prioritize this. Both extension and CLI doesn't have this. Switching to Claude Code for now.

[apoorv-garg-31]

resuming a previous conversation is very important, in-cases where system or codex hangs or accidently pressed CTRL+C twice, we are out from the codex and unable to resume a previous conversation.

[dayowe]

yeah, accidental ctrl-c twice just happened to me in the middle of an implementation. Would be nice if exiting the session needed to be confirmed..considering that there's no way to resume. the hint of @zacharypodbela below helped get Codex up to speed again!

[zacharypodbela]

Wow yea broken without this.

As a workaround for now, you can find files with messages from previous sessions in ~/.codex/sessions/$YEAR/$MONTH/$DAY/ and then start your newest session with:

▌Please start by reading ~/.codex/sessions/$YEAR/$MONTH/$DAY/$FILE_NAME.jsonl to get caught up
▌on what we did in our previous session.

[am-will]

you could religiously have codex output important context to a md file to resume at a later time, but much like compactification, you run the risk of it missing important context for the next session. That said, it's way better than nothing.

[dayowe]

Wow, can't believe this isn't possible. Major inconvenience

[fyne-coder]

It is just shipped in 0.30.0 - look at the release notes

[am-will]

Heck yeah @aibrahim-oai you're a legend

…

On Sat, Sep 6, 2025, 11:47 AM Arthur Lee ***@***.***> wrote: It is just shipped in 0.30.0 - look at the release notes — Reply to this email directly, view it on GitHub <#1076 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKD57ZDFDRNZN5TTYZU6SMD3RMM4FAVCNFSM6AAAAAB5VUBCNWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZSHAYTONY> . You are receiving this because you commented.Message ID: ***@***.***>

[davej]

@fyne-coder what am I missing? Doesn't seem to be working for me!

[alanhe421]

I feel that an experience similar to Claude is more comfortable: first enter through codex, then use /resume to select the conversation.

[PeterP22]

codex resume worked for me! thanks j-carin

[alfondotnet]

would be neat if they added a /resume like claude code

[am-will]

I feel that an experience similar to Claude is more comfortable: first enter through codex, then use /resume to select the conversation.

Disagree, that's literally an additional unnecessary step. I'd be fine if they added it, but there's no great argument for this.

You're asserting that running 'codex' first, waiting for it to load and then typing /resume is better than skipping all that and just typing 'codex resume' and jumping straight into it? No. Not better, easier, or faster.

Not against them adding it of course, would be nice to have if you already happen to be talking to codex but that's about it.

[lingtaolf]

can try https://github.com/lingtaolf/cxresume