When the Chrome extension isn't connected, Claude is pointed at /chrome instead of flailing.
What's wrong with this entry?
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.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
Browser tabs: Claude is told to close tabs it opened
Both mention chrome browser
-
v2.1.221
Chrome bridge gains roster change notifications, retained tool args and permission categories
Both mention chrome browser
-
v2.1.221
Chrome bridge gains an activity-observer hook, not wired up
Both mention chrome browser