claude-code - 💡(How to fix) Fix [DOCS] Claude in Chrome docs omit connected-browser selection behavior

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…
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/chrome

Section/Topic

Get started in the CLI, the /chrome connection-management guidance, and troubleshooting for sessions with multiple connected browsers.

Current Documentation

The Chrome page currently explains how to enable and manage the integration:

You can also enable Chrome from within an existing session by running /chrome.

It later says:

Run /chrome at any time to check the connection status, manage permissions, or reconnect the extension.

The command reference only summarizes the slash command:

/chrome | Configure Claude in Chrome settings

No current documentation explains that /chrome can select which connected browser to use, or that Claude prompts in chat when a browser action runs while multiple browsers are connected.

What's Wrong or Missing?

The v2.1.154 release entry says:

Claude in Chrome: pick which connected browser to use via /chrome → "Select browser...", or in-chat when a browser action runs with multiple connected

The docs describe Chrome/Edge support, extension setup, connection status, permissions, and reconnect behavior, but they omit the browser-selection flow for users with more than one connected browser.

That leaves three user-visible gaps:

A. /chrome selection menu is undocumented

Users are told to run /chrome for status, permissions, and reconnecting, but not that it now includes a "Select browser..." option.

B. Multiple connected browser behavior is undocumented

The page says Claude uses a visible browser window and can use Chrome or Edge, but it does not explain what happens when multiple supported browsers or extension connections are available at the same time.

C. In-chat fallback prompt is undocumented

The release notes say Claude can ask in chat when a browser action runs with multiple connected browsers. The Chrome docs do not mention this prompt, so users may not know why a browser action pauses for selection or how to resolve it.

Suggested Improvement

Update https://code.claude.com/docs/en/chrome to document connected-browser selection.

Suggested addition near the /chrome connection-management paragraph:

If multiple supported browsers are connected, run /chrome and choose "Select browser..." to pick which browser Claude should use for browser actions. If you start a browser action while multiple browsers are connected and no browser is selected, Claude prompts you in chat to choose one before continuing.

Also consider adding a troubleshooting note for users who expected Claude to use a different browser:

If Claude opens or controls the wrong browser, run /chrome and use "Select browser..." to switch the active connected browser.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/chromePrimary Claude in Chrome setup, connection management, and troubleshooting page
https://code.claude.com/docs/en/commands/chrome command summary says it configures Claude in Chrome settings but does not mention browser selection
https://code.claude.com/docs/en/vs-codeBrowser automation section points to the Chrome page for setup and troubleshooting, so the primary fix should live there

Total scope: 3 pages affected

Version context: Behavior described by the v2.1.154 release entry for Claude in Chrome connected-browser selection.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING