Repository navigation
/undo only reverts conversation, not code changes across repositories #26488
Description
Description
I encountered an issue with /undo when using opencode across multiple Git repositories.
My opencode session was started inside repository A, but during the session I modified files inside repository B.
When I executed:
/undoonly the conversation history was reverted.
The code changes inside repository B were NOT reverted.
Expected Behavior
/undo should either:
- Revert all file changes made during the last assistant turn, including cross-repository edits
OR
- Clearly warn/document that
/undoonly tracks changes inside the current session repository.
Actual Behavior
- Conversation rollback works
- Changes in repository
Amay rollback - Changes in repository
Bremain unchanged
This can be dangerous because users may assume /undo restores all AI-generated modifications.
Reproduction Steps
- Start opencode inside repository
A - Ask the assistant to modify files in repository
B - Execute
/undo - Observe that repository
Bchanges are not reverted
Environment
- macOS Apple Silicon (M2)
- opencode latest version
- multiple Git repositories
Suggestion
Possible improvements:
- Track all modified repositories during a session
- Extend
/undoto support cross-repository rollback - Or explicitly limit/document
/undoscope in the UI/docs
Metadata
Metadata
Assignees
Labels
No labels
Activity
[-] only reverts conversation, not code changes across repositories[/-][+]`/undo` only reverts conversation, not code changes across repositories[/+]github-actions commentedon May 9, 2026
This issue might be a duplicate of existing issues. Please check:
/undocommand only rolls back AI conversation message, not the associated file changes #5474:/undocommand only rolls back AI conversation message, not the associated file changes/undoand/timelineundo does not revert file editsYour report adds a specific cross-repository scenario (changes in repo B not reverted when session is started in repo A), which may be a distinct edge case worth tracking separately. Please review the above issues and comment there if your situation is covered, or clarify how your case differs.
lightrao commentedon May 9, 2026
Thanks for checking and linking those issues.
I reviewed #5474 and #4704. They cover the more general case where
/undodoes not revert file edits, including cases within the active project/repository.The distinction in this report is the repository boundary:
AB/undorolls back the conversation, but the changes in repositoryBremainSo this may be related to the same undo/snapshot mechanism, but the specific edge case is cross-repository edits made from a single session. If
/undois intentionally scoped only to the session's initial repository/worktree, then a warning or documentation note would address the safety issue. If it is intended to revert the last assistant turn regardless of which repository was modified, then repoBshould probably be tracked as part of the undo state too.github-actions commentedon Jul 9, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.