Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Claude in Chrome (Beta) feature blocked on Windows native — flag exists but slash command unavailable [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#53372•Fetched 2026-04-26 05:17:28
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
DexterPro21DexterPro21
Participants
DexterPro21DexterPro21github-actions[bot]github-actions[bot]
Timeline (top)
labeled ×5commented ×1unlabeled ×1

Error Message

Error Messages/Logs

Fix Action

Fix / Workaround

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

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

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

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • 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

extent analysis

TL;DR

The issue might be due to a lack of support for Claude in Chrome on Windows native, despite the presence of the --chrome flag, and a workaround or documentation clarification is needed.

Guidance

  • Verify if Claude in Chrome is officially supported on Windows native by checking the official documentation or changelog, as the current information only mentions support for WSL environments.
  • Check the settings.json file for any missing configurations or sections that might be required for Claude in Chrome to work, such as the mcpServers section.
  • Attempt to register the claude-in-chrome tool manually or check if there are any specific instructions for setting it up on Windows native.
  • If the feature is not supported, consider using a different environment, such as WSL, or wait for an update that includes support for Windows native.

Notes

The issue seems to be related to a potential lack of support for Claude in Chrome on Windows native, but without further information or official documentation, it's difficult to provide a definitive solution.

Recommendation

Apply workaround: Check the official documentation or wait for an update that includes support for Windows native, as the current version might not be compatible.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#indexing error#inference speed#output truncation#response parsing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING