[BUG] Claude in Chrome (Beta) feature blocked on Windows native — flag exists but slash command unavailable

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?

Title: Claude in Chrome (Beta) feature blocked on Windows native — flag exists but slash command unavailable

Environment:

• OS: Windows (native, no WSL)
• Claude Code version: 2.1.119
• Plan: Claude Max (Opus 4.7)
• Chrome version: latest stable
• Chrome extension "Claude" v1.0.69 (ID fcoeoabgfenejglbffodgkkbkcdhcgfn) installed and verified in

C:\Users\<user>\AppData\Local\Google\Chrome\User Data\Default\Extensions\

Symptoms:

1. Flag --chrome appears in claude --help output: "--chrome Enable Claude in Chrome integration"
2. Started Claude Code with claude --chrome from cmd (.bat wrapper)
3. Slash command /chrome returns: "isn't available in this environment"
4. mcp__claude-in-chrome__* tools never load (qa-browser subagent reports empty toolset)
5. settings.json has no mcpServers section, never had claude-in-chrome registered (verified in 5 backup files of .claude.json)

Expected: --chrome flag should activate Chrome MCP tools (navigate, form_input, read_page, etc.)
Actual: Flag accepted but tools not loaded; /chrome command blocked

Impact:

• Cannot run visual QA via Chrome MCP
• Wasted ~3 hours of debugging + ~50K tokens on this session trying to diagnose
• Blocks completion of QA Fase 2 backup hybrid commits (5dec1da, d07468c, 9c5353e)

Reproducible: yes, every session.
Workaround attempted: full Claude Code restart, PC reboot, .bat wrapper with --chrome, /mcp slash inspect — none worked.

Request: clarify if Claude in Chrome supports Windows native (changelog mentions "Fixed Claude in Chrome support for WSL environments" but not Windows native). If supported, debug help. If not supported, document clearly.

What Should Happen?

Title: Claude in Chrome (Beta) feature blocked on Windows native — flag exists but slash command unavailable

Environment:

• OS: Windows (native, no WSL)
• Claude Code version: 2.1.119
• Plan: Claude Max (Opus 4.7)
• Chrome version: latest stable
• Chrome extension "Claude" v1.0.69 (ID fcoeoabgfenejglbffodgkkbkcdhcgfn) installed and verified in

C:\Users\<user>\AppData\Local\Google\Chrome\User Data\Default\Extensions\

Symptoms:

1. Flag --chrome appears in claude --help output: "--chrome Enable Claude in Chrome integration"
2. Started Claude Code with claude --chrome from cmd (.bat wrapper)
3. Slash command /chrome returns: "isn't available in this environment"
4. mcp__claude-in-chrome__* tools never load (qa-browser subagent reports empty toolset)
5. settings.json has no mcpServers section, never had claude-in-chrome registered (verified in 5 backup files of .claude.json)

Expected: --chrome flag should activate Chrome MCP tools (navigate, form_input, read_page, etc.)
Actual: Flag accepted but tools not loaded; /chrome command blocked

Impact:

• Cannot run visual QA via Chrome MCP
• Wasted ~3 hours of debugging + ~50K tokens on this session trying to diagnose
• Blocks completion of QA Fase 2 backup hybrid commits (5dec1da, d07468c, 9c5353e)

Reproducible: yes, every session.
Workaround attempted: full Claude Code restart, PC reboot, .bat wrapper with --chrome, /mcp slash inspect — none worked.

Request: clarify if Claude in Chrome supports Windows native (changelog mentions "Fixed Claude in Chrome support for WSL environments" but not Windows native). If supported, debug help. If not supported, document clearly.

Error Messages/Logs

Steps to Reproduce

Title: Claude in Chrome (Beta) feature blocked on Windows native — flag exists but slash command unavailable

Environment:

• OS: Windows (native, no WSL)
• Claude Code version: 2.1.119
• Plan: Claude Max (Opus 4.7)
• Chrome version: latest stable
• Chrome extension "Claude" v1.0.69 (ID fcoeoabgfenejglbffodgkkbkcdhcgfn) installed and verified in

C:\Users\<user>\AppData\Local\Google\Chrome\User Data\Default\Extensions\

Symptoms:

1. Flag --chrome appears in claude --help output: "--chrome Enable Claude in Chrome integration"
2. Started Claude Code with claude --chrome from cmd (.bat wrapper)
3. Slash command /chrome returns: "isn't available in this environment"
4. mcp__claude-in-chrome__* tools never load (qa-browser subagent reports empty toolset)
5. settings.json has no mcpServers section, never had claude-in-chrome registered (verified in 5 backup files of .claude.json)

Expected: --chrome flag should activate Chrome MCP tools (navigate, form_input, read_page, etc.)
Actual: Flag accepted but tools not loaded; /chrome command blocked

Impact:

• Cannot run visual QA via Chrome MCP
• Wasted ~3 hours of debugging + ~50K tokens on this session trying to diagnose
• Blocks completion of QA Fase 2 backup hybrid commits (5dec1da, d07468c, 9c5353e)

Reproducible: yes, every session.
Workaround attempted: full Claude Code restart, PC reboot, .bat wrapper with --chrome, /mcp slash inspect — none worked.

Request: clarify if Claude in Chrome supports Windows native (changelog mentions "Fixed Claude in Chrome support for WSL environments" but not Windows native). If supported, debug help. If not supported, document clearly.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.119

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

_No response_