v1.2.0 - Wrapper-Specific CLI Switches

New Features

Wrapper-Specific CLI Switches

This release adds dedicated CLI switches for the wrapper itself, separate from Claude Code CLI passthrough:

• --wrapper-version - Show wrapper version and exit
• --wrapper-help - Show wrapper-specific help and exit
• --wrapper-test - Run comprehensive passthrough test and exit

All wrapper flags use the --wrapper- prefix to avoid conflicts with Claude Code CLI flags.

Built-in Testing

The new --wrapper-test command provides comprehensive verification:

1. Configuration check (verifies config file loading)
2. Node.js existence check
3. Claude Code CLI existence check
4. Actual passthrough test (runs claude --version)

This is especially useful after Claude Code updates to confirm the wrapper still works correctly.

Example Usage

REM Show wrapper version
claude-wrapper.exe --wrapper-version

REM Run comprehensive test
claude-wrapper.exe --wrapper-test

REM Regular passthrough still works
claude-wrapper.exe --version
claude-wrapper.exe --help

Installation

1. Download claude-wrapper.exe and claude-wrapper.example.json
2. Copy to a permanent location (e.g., C:\Tools)
3. Rename claude-wrapper.example.json to claude-wrapper.json
4. Edit claude-wrapper.json with your Node.js and CLI paths
5. Update VS Code settings.json:

   {
     "claudeCode.claudeProcessWrapper": "C:\Tools\claude-wrapper.exe"
   }

What Changed

• Added wrapper-specific CLI handling before passthrough
• Updated README.md with CLI usage documentation
• Updated test.bat with note about built-in test command
• Bumped version to 1.2.0

See full details: https://github.com/Gronsten/claude-wrapper/blob/main/README.md