[FEATURE] Implement all CLI commands in Claude Code VS Code Extension + /rewind priority

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

Currently, the Claude Code VS Code extension lacks feature parity with the CLI version, particularly missing essential commands that are available in the command-line interface. This creates an inconsistent experience between the two environments and limits the extension's capabilities.
Feature Request

Proposed Solution

I would like to request the implementation of all CLI commands within the VS Code extension, including but not limited to:

/rewind - Ability to revert to previous states in the conversation/coding session
/undo - Undo the last action or generated code
/retry - Retry the last request with the same parameters
/save - Save the current session state
/load - Load a previously saved session
/diff - Show differences between code versions
/help - Display available commands and their usage
Any other commands currently available in the CLI version

Use Cases

Workflow Continuity: Developers who switch between CLI and VS Code should have access to the same command set
Error Recovery: /rewind and /undo are crucial for quickly recovering from unwanted changes
Iteration Speed: /retry allows for quick refinements without retyping requests
Session Management: /save and /load enable persistent workflows across coding sessions

Expected Behavior

Commands should be accessible through:
The command palette (Cmd/Ctrl+Shift+P)
Direct typing in the Claude Code chat interface (with / prefix)
Keyboard shortcuts for frequently used commands

Commands should maintain the same syntax and behavior as their CLI counterparts
Benefits

Consistency: Unified experience across all Claude Code interfaces
Productivity: Reduced context switching between tools
Accessibility: Makes powerful CLI features available to VS Code users who prefer GUI environments
Learning Curve: Easier transition between CLI and extension usage

Additional Context
Having full command parity would significantly enhance the developer experience and make the VS Code extension a complete alternative to the CLI, rather than a limited subset. This is particularly important for teams that have standardized on VS Code as their primary development environment.
Priority
High - These commands are fundamental to efficient AI-assisted development workflows and their absence creates a significant gap in functionality.

Would love to hear if this is on the roadmap and if there's any timeline for implementation. Happy to provide more specific use cases or testing feedback if needed.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_