feat: a basic session management #776
Open
+8,740
−19
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
edoardoc
changed the title
edoardoc
changed the title
edoardoc
force-pushed
the
feat/session-support
branch
2 times, most recently
from
2432dd7 to
f53ebf0
Compare
edoardoc
added a commit
to edoardoc/codex
that referenced
this pull request
May 4, 2025
edoardoc
changed the title
edoardoc
changed the title
edoardoc
force-pushed
the
feat/session-support
branch
from
f1ce79f to
72dea5d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A basic session management option
new parameter -S / --session : start or continue a named session
new params:
--session-list|--session-path|--session-dump|--session-deleteto manage saved sessionsSession logs now include the last OpenAI response_id alongside message history
On restart, it reloads both messages and response_id, then call /responses.create({ previous_response_id }) so the model picks up exactly where it left off
Interrupting mid-stream (Ctrl+C) and rerunning codex -S foo … seamlessly resumes in-flight