[FEATURE] Add /undo command support in VS Code extension

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

The lack of /undo or /rewind commands makes very difficult to revert changes from a specific interaction without manually discarding files or using git commands. Specially when we do multiple interactions in the same chat without doing commits. This is a critical gap for iterative development workflows.

During a multi-turn chat session in VS Code, Claude Code may make changes across multiple files in a single interaction that don't produce the desired result. Currently, there is no quick way to revert just the last interaction's changes.

Cursor already has this functionality built in — you can revert the changes from any specific interaction with a single click. Not having this basic feature in the VS Code extension makes it very hard to justify continuing to use (and pay for) Claude Code over alternatives that already solve this.

The absence of this feature assumes the AI will always produce correct changes on the first try, which is not realistic. Iterating with an AI coding assistant means frequently needing to revert and retry. Without a quick undo mechanism, the feedback loop becomes frustrating and slow, which defeats the purpose of using an AI assistant in the first place.

Proposed Solution

/undo or /rewind should be available as a slash command in the VS Code extension input, reverting all file edits from the most recent interaction while preserving changes from earlier interactions in the same session.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

1. Start working on a feature, give it a prompt
2. Everything is ok, give it a second prompt with specifications that are incorrect
3. Try to revert the last changes of the second prompt, maintaining the changes from the first one. Working on the same files, same code blocks, and so on.

Additional Context

_No response_