Memory for previous chats

[nectario]

Codex is amazing. Love it! Some of my projects can take multiple days. I just wish if I could continue off where I left off the next day. Can the chat history text be automatically injected, if you stop and start off the next day?

[JoshuaSoileau]

+1 I have the same problem.

There should really be a built in solution to reviving previous sessions.

In the meantime, I hacked my way into this by getting codex to document our conversations into a file, and then I share that file at the beginning of subsequent conversations if I want to pass the old context forward to a new session.

Here's what I put in my ~/.codex/instructions.md:

## Track your most recent session notes in `/Users/joshuasoileau/.codex/latest-session.md` (MANDATORY)

During all sessions, keep a record of the discussion happening in a markdown file in /Users/joshuasoileau/.codex/latest-session.md.

That markdown file should have the format:

\`\`\`
The most recent discussion I had with codex was the following. Please use these notes as informative context, so you can catch up and we can re-start the conversation accordingly.

# Topic: <discussion topic>

## User desires
<Brief description of what the user wants, the overall purpose and goal>

## Specifics of user desires
<More detailed version of the above, with details about specific the user is looking for>

## Actions taken
<List of steps taken to help the user>

## Helpful hints about conversation & relevant code paths:
<List of hints or codepaths that were particularly informative or helpful during the session>

With this context in mind, I have a follow up query:
\```


## Session-notes rule (MANDATORY)

- After **every** assistant turn the agent **MUST** update `/Users/joshuasoileau/.codex/latest-session.md` with the standard template.

- Skipping this step is considered a violation of the instructions.

As we have conversations, I want you to update this file every time you complete a response, with updated details about the conversation/session to that point.

[nectario]

Yeap, I have it summarize our chat thread with all solutions and challenges in a text file allowing me to continue the next day.

[nectario]

This is great. Thanks for sharing.

[edoardoc]

indeed a good idea, but then I cant understand what is the meaning of the History Configuration? I thought there is a file saved somewhere where history gets saved? something like what chatblade does with sessions

[edoardoc]

following up on my own question, History is only for repeating queries: no session management

[edoardoc]

I drafted a session parameter in this mr, when starting it with codex --session foo it will create a new session and via subsequent restarts it will "remember where it was left off.
Works only with openai, cause only that one has the response_id parameter afaik