Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.268 ·

Browser MCP tools gain a global isDisabled kill-switch

Browser-control tools like switch_browser, list_connected_browsers, and select_browser now check a kill-switch before acting

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaChrome & Browserwhat it touches
KindBug Fixesin v2.1.268,
Group of 4 Under the hood No documentation found

Browser-control tools like switch_browser, list_connected_browsers, and select_browser now check a kill-switch before acting

What

The Chrome/browser MCP tool-call path now checks isDisabled?.() before doing any work, across dispatch, tabs_context lookup, switch_browser, list_connected_browsers, select_browser, connection watchers, and tool listing. When it's disabled:

  • list_connected_browsers returns Unknown tool: list_connected_browsers instead of running.
  • switch_browser and the computer-use 'type' action return a disabled/'Unknown tool' response instead of proceeding.
  • select_browser returns Unknown tool: select_browser; its success message also changed from 'Connected to browser' to 'Selected browser'.

Why

This gives Claude Code a single, central way to turn off browser-control tools entirely (for example, in an environment where automated browser control shouldn't be available) rather than needing each tool to fail in its own way.

Read from
Names in the bundleswitch_browser

See this entry in the whole of v2.1.268 →

Feedback