Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.273entry #4

Claude Code v2.1.273 ·

New --chrome flag for spawned and remote-control sessions

A new --chrome / --no-chrome flag controls whether spawned and Remote Control sessions can use Claude in Chrome

Group of 4 Use it now Notable New Features
JSON All of v2.1.273
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ChromeArea: what it touches
New FeaturesKind: in v2.1.273,
What probably matters to youSection of the release

What

  • Spawning or reattaching a session now supports a --[no-]chrome flag that controls whether "Claude in Chrome" is available for that session, defaulting to the machine's own Chrome setting.
  • The claude remote-control command's argument parser also gained matching --chrome/--no-chrome flags.
  • When Remote Control starts with --chrome, Claude Code now checks whether an enterprise MCP policy or a denied-MCP-servers list blocks the Claude-in-Chrome MCP server, and exits with an error instead of silently proceeding if it's blocked.
  • Child sessions spawned by Remote Control now inherit the --chrome setting from their parent, so the option is passed through consistently.

Why

This gives explicit, per-session control over whether Claude in Chrome is enabled, and ensures that enterprise policies restricting MCP servers (which Claude in Chrome relies on) are respected rather than bypassed when Remote Control starts with Chrome access requested.

Read from
Names in the bundle--chrome--no-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 --no-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
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 --no-chrome, on CLI reference. | `--no-chrome` | Disable [Chrome browser integration](/docs/en/chrome) for this session | `claude --no-chrome` | cli-reference see the edit
Confirmed since Anthropic's documentation has since written up --chrome, on CLI reference. | `--chrome` | Enable [Chrome browser integration](/docs/en/chrome) for web automation and testing | `claude --chrome` | cli-reference see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --chrome, on CLI reference.

See this entry in the whole of v2.1.273 →

Feedback