Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.290entry #60

Claude Code v2.1.290 ·

Better handling when the Claude in Chrome connection fails

/chrome now shows the real Claude in Chrome connection state with a working Reconnect, and Claude is told to skip browser tools while it is down

Group of 2 Use it now Improvements
JSON All of v2.1.290
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Chrome & BrowserArea: what it touches
ImprovementsKind: in v2.1.290,
What probably matters to youSection of the release

Unclear It is not clear which kinds of session can reconnect directly from the /chrome dialog.

What

Claude in Chrome lets Claude control your browser. It connects through MCP (Model Context Protocol), the way Claude Code links to outside tools. When that connection has failed or been turned off, Claude Code now handles it more clearly:

  • The /chrome menu shows the real connection state: connected, connecting, failed, disabled or absent. Before, it showed only Enabled or Disabled.
  • The "Reconnect extension" action now actually tries to reconnect. Before, it only opened a link. When it cannot reconnect, it says why: Chrome was not turned on for this session (start with claude --chrome), the session uses an API key or long-lived token (run /login), or Claude in Chrome was turned off in /mcp (open /mcp, select claude-in-chrome and turn it on).
  • A notice tells Claude that Claude in Chrome is turned on for the session but the browser connection is not working. Claude is told not to try the mcp__claude-in-chrome__* tools and to use WebFetch and WebSearch instead. The notice also points you to /chrome (Reconnect extension) or /mcp to restore the connection. The findings did not trace when this notice is added.

Why

With a dead browser connection, you get a Reconnect button that works and a message saying what to do. Claude is steered toward the other web tools instead of repeatedly calling browser tools that cannot respond.

Read from
Names in the bundle/chrome
Since it was published

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 Troubleshoot Claude Science. For the steps, see the help for [Chrome](https://support.google.com/chrome/answer/2693767), [Safari](https://support.apple.com/guide/safari/customize-settings-per-website-ibrw7f78f7fe/mac), [macOS](https://support.apple.com/guide/mac-help/… claude-science/troubleshooting see the edit
Added since A small documentation edit on Use Claude Code with Chrome touched a line naming /chrome after this was published. | "Browser extension is not connected" | Native messaging host cannot reach the extension, or your organization's IP allowlist rejects the connection to `bridge.claudeusercontent.com` | Check that the extension is signed in to the same cla… chrome see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which kinds of session can reconnect directly from the `/chrome` dialog.
Anthropic's documentation agreesA small documentation edit on Use Claude Code with Chrome touched a line naming /chrome after this was published.
Anthropic's release notes agreeFixed /chrome "Reconnect extension" not restoring browser tools after a failed Chrome connection, and added an explanation when it can't…

See this entry in the whole of v2.1.290 →

Feedback