[BUG] `/plugin` command not recognized in v2.0.13 on Windows 10 (Terminal/PowerShell)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

The /plugin command is not recognized despite running Claude Code version 2.0.13. When attempting to use any /plugin sub-command (e.g., /plugin marketplace), I receive the error: "Unknown slash command: plugin"

Per the release notes, a fix for plugin support was introduced in v2.0.13 for native builds, but the command still does not seem to work.

What Should Happen?

The /plugin command should be recognized and provide access to plugin functionality.

Error Messages/Logs

> /plugin marketplace
Unknown slash command: plugin

Steps to Reproduce

1. Launch Claude Code v2.0.13 on Windows 10 using PowerShell/Windows Terminal
2. Type /plugin marketplace (or any other /plugin sub-command)
3. Press Enter
4. Observe error: "Unknown slash command: plugin"

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

N/A

Claude Code Version

2.0.13

Platform

Other

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Installation Details:

• Node.js version: v20.11.0
• Installation method: Local installation (not global npm)
• Installation path: C:\Users\Mark\.claude\local\node_modules\.bin\claude

Environment:

• Running on Windows 10 via Git Bash (MSYS environment)
• System info: MINGW64_NT-10.0-19045 Mark 3.4.10-87d57229.x86_64

Observations:

• All other slash commands appear to work correctly
• The v2.0.13 release notes specifically mention: "Fixed /plugin not working on native build"
• This suggests the issue may be specific to Windows/MSYS environments or may require additional investigation

Possible Causes:

1. The native build fix in v2.0.13 may not fully resolve issues in Windows PowerShell environments
2. Local installation vs global installation may affect plugin command availability
3. Additional setup or configuration may be required for Windows environments