Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.282entry #29

Claude Code v2.1.282 ·

Claude in Chrome can be allowed alongside managed-mcp.json, with policy-specific refusals

New allowClaudeInChromeWithManagedMcp policy lets admins permit Claude in Chrome under managed-mcp.json, and blocked setups now explain why

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

Unclear Which specific refusal reasons the new message can report is not known.

What

Claude in Chrome is the browser integration, delivered as a built-in MCP server (MCP is a standard for connecting outside tools). Organizations that deploy a managed MCP configuration, managed-mcp.json, take exclusive control of which MCP servers run, and that used to block Claude in Chrome with no way to allow it.

  • A new device policy key, allowClaudeInChromeWithManagedMcp, is off by default. When it is true and the enterprise configuration was read without fatal errors, Claude in Chrome can run alongside managed-mcp.json. deniedMcpServers and the organization's Claude in Chrome setting can still block it.
  • Without the key, trying to configure Chrome is refused with a Chrome-specific message: "Claude in Chrome is blocked by your organization's managed MCP configuration (managed-mcp.json). An administrator can allow it with allowClaudeInChromeWithManagedMcp in device policy." Before, it got the generic "You cannot dynamically configure MCP servers when an enterprise MCP config is present" message.
  • The prompt offering to install or set up Claude in Chrome is now also skipped when managed-mcp.json blocks Chrome. Before, only deniedMcpServers was checked.
  • Starting Remote Control with --chrome under a blocking policy now prints the specific reason Chrome is blocked, followed by "Start Remote Control without --chrome." It used to print one fixed message naming both an enterprise MCP config and a deniedMcpServers entry.

Why

Administrators using managed-mcp.json can now opt in to Claude in Chrome. Where it stays blocked, people are no longer offered a setup that cannot work, and error messages name the policy responsible.

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.

Added since A small documentation edit on Continue local sessions from any device with Remote Control touched a line naming --chrome after this was published. | `--chrome` / `--no-chrome` | Turn [Chrome integration](/docs/en/chrome) on or off in the sessions the server creates, so Claude can use Chrome on your machine while you work from another device. Without either flag, the session the serve… remote-control see the edit
Confirmed since Anthropic's documentation has since written up --chrome, on All settings. | [`claudeInChromeDefaultEnabled`](#claudeinchromedefaultenabled) | Turn on [Chrome integration](/docs/en/chrome) in every interactive CLI session without passing `--chrome` | Global config settings | Global config | settings-reference 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 doubtWhich specific refusal reasons the new message can report is not known.
Anthropic's documentation agreesAnthropic's documentation has since written up --chrome, on All settings.
Anthropic's release notes agreeAdded the allowClaudeInChromeWithManagedMcp managed setting to let claude --chrome run alongside an exclusive managed-mcp.json; the error…

See this entry in the whole of v2.1.282 →

Feedback