You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a808632
Browse filesBrowse the repository at this point in the historyBrowse files
Add task --resume-thread <id> for explicit thread resume
--resume/--resume-last picks the newest tracked task thread, which is
ambiguous for orchestrators driving several concurrent Codex jobs in one
repository: the thread that gets resumed depends on job-store state and
session scoping rather than the caller's intent. The app-server layer
already supports targeting a thread (runAppServerTurn resumeThreadId);
this exposes it on the task subcommand so callers that recorded a
threadId from a previous run (task --json) can continue that exact
conversation.
- task --resume-thread <id> resumes the given thread (foreground and
--background; the worker path serializes resumeThreadId through the
stored request)
- conflicts with --resume/--resume-last/--fresh are rejected
- a prompt remains optional, matching --resume-last semantics
Co-Authored-By: Claude Fable 5 <[email protected]>
(cherry picked from commit 84d82a4)
0 commit comments