Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Claude in Chrome can come from the remote session host instead of the built-in server

If the remote host supplies Claude in Chrome through --mcp-config, Claude Code uses that and does not start its own Chrome server

You'll notice Improvements
JSON All of v2.1.285
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Chrome & BrowserArea: what it touches
ImprovementsKind: in v2.1.285,
ImprovementsSection of the release
What

Claude in Chrome lets Claude Code work with your Chrome browser. It runs as an MCP server, a small add-on program that gives Claude Code extra tools. Before, Claude Code always started its own built-in Chrome server.

Now, if the remote session host supplies a Claude in Chrome server through --mcp-config, Claude Code does not start the built-in one. One of three things then happens:

  • A deniedMcpServers policy blocks the entry, and it is dropped.
  • An organization policy denies the extension, and the entry is not used.
  • Otherwise the entry is used, and a matching instruction is added to Claude's system prompt.
Why

Browser tools supplied by the remote host now take priority over the local built-in server, while existing admin policies can still block them.

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 doubtHow Claude Code recognises that an entry came from the remote host is not known.
Anthropic's release notes agreeChanged MCP tools so a tool that sets its own _meta['anthropic/alwaysLoad'] to false stays deferred when its --mcp-config, Agent SDK or…

See this entry in the whole of v2.1.285 →

Feedback