What
When the browser extension is not set up, Claude is told browser tools are unavailable, pointed at /chrome and the install surface, and told not to try the Chrome tools anyway.
Evidence
Do not attempt mcp__claude-in-chrome__* tool calls.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/chrome
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up /chrome, on Overview.
| Debug live web applications | [Chrome](/docs/en/chrome) |overview see the edit
Added since
A small documentation edit on Set up Claude Code for your organization touched a line naming /chrome after this was published.
Some Claude Code features require a claude.ai account. [Cloud sessions](/docs/en/claude-code-on-the-web), [Routines](/docs/en/routines), [Code Review](/docs/en/code-review), [Remote Control](/docs/en/remote-control), and the [Chrome extens…admin-setup see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Set up Claude Code for your organization touched a line naming /chrome after this was published.