-
Notifications
You must be signed in to change notification settings - Fork 174
Fix Codex resume failure due to improper --last usage #188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
codex resumecommand is missing the session identifier or--lastflag, which means the CLI won't know which session to resume. This breaks session resumption for continued conversations.View Details
📝 Patch Details
Analysis
Missing session identifier in
codex resumecommandWhat fails: The
executeCodexInSandbox()function inlib/sandbox/agents/codex.ts(lines 283-297) builds acodex resumecommand that doesn't specify which session to resume when continuing a conversation in a kept-alive sandbox.How to reproduce:
executeCodexInSandbox()withisResumed=trueand a validsessionIdparametercodex resume(no session identifier)codex resumewith no arguments opens an interactive pickerResult: The Codex CLI fails to resume the session. According to Codex documentation:
codex resume= opens interactive picker (fails in non-interactive sandbox)codex resume --last= resumes most recent sessioncodex resume <SESSION_ID>= resumes specific session by IDThe
sessionIdparameter is passed to the function (line 35) and available, but was never used after commit5d8487eremoved the--lastflag without adding sessionId support.Expected:
sessionIdis provided: usecodex resume <sessionId>sessionIdis not provided: fall back tocodex resume --lastThis follows the pattern used by other agents (Claude, Cursor, Copilot) that also handle session resumption.