`/undo` only reverts conversation, not code changes across repositories

[lightrao]

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:

/undo

only the conversation history was reverted.

The code changes inside repository B were NOT reverted.

Expected Behavior

/undo should either:

1. Revert all file changes made during the last assistant turn, including cross-repository edits

OR

2. Clearly warn/document that /undo only tracks changes inside the current session repository.

Actual Behavior

• Conversation rollback works
• Changes in repository A may rollback
• Changes in repository B remain unchanged

This can be dangerous because users may assume /undo restores all AI-generated modifications.

Reproduction Steps

1. Start opencode inside repository A
2. Ask the assistant to modify files in repository B
3. Execute /undo
4. Observe that repository B changes 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 /undo to support cross-repository rollback
• Or explicitly limit/document /undo scope in the UI/docs

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• /undo command only rolls back AI conversation message, not the associated file changes #5474: /undo command only rolls back AI conversation message, not the associated file changes
• /undo and /timeline undo does not revert file edits #4704: /undo and /timeline undo does not revert file edits

Your 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]

Thanks for checking and linking those issues.

I reviewed #5474 and #4704. They cover the more general case where /undo does not revert file edits, including cases within the active project/repository.

The distinction in this report is the repository boundary:

• opencode is started from Git repository A
• the assistant edits files in a separate Git repository B
• running /undo rolls back the conversation, but the changes in repository B remain

So 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 /undo is 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 repo B should probably be tracked as part of the undo state too.