Repository navigation
New proposal (related to #3600): Add codex continue to resume latest work in current directory #4342
Description
What feature would you like to see?
Currently, codex resume helps pick up from past work, but it is not always convenient when working across multiple repositories. I propose that codex continue should automatically resume the most recent Codex work in the current directory. This would make it consistent with the idea of codex resume, but simpler and more intuitive for ongoing local work.
Are you interested in implementing this feature?
Yes, I’d like to work on it.
Additional information
Related to Issue #3600, but focuses on adding codex continue to resume the latest work in the current directory.
Activity
lox commentedon Sep 28, 2025
I'd love to see this as well, also happy to implement.
dedrisian-oai commentedon Sep 30, 2025
codex resume --lastworks the same way! You could add an alias too, if you want it simpler.Closing the issue for now.
Nhahan commentedon Oct 1, 2025
@dedrisian-oai
Thanks for the quick reply! I think there’s a misunderstanding about the scope.
codex resume --lastresumes the latest Codex session globally (across all directories on the machine).My request was to resume the latest session within the current directory/workspace only.
Concretely, I’m proposing a UX like:
codex continue→ resume the most recent session whose workspacePath (or equivalent) matches the current directory (or its subdir).Why this matters:
--lastoften resumes an unrelated repo’s session.Possible designs (any of these would solve it):
codex resume --last-in-dirorcodex resume --continuecodex resume --last --scope=dir(default: global)lox commentedon Oct 2, 2025
I have been using this implementation in my fork for a week or so, along with a fix to sort by mtime not ctime, it works well:
#4604
williamhrs commentedon Oct 3, 2025
this would be awesome
Nhahan commentedon Oct 10, 2025
Please check #4545
cc. @dedrisian-oai