Skip to content
← Back to release · 2.1.290
Improvements / v2.1.290

Block project settings from enabling Chrome

CHANGELOG · original

Changed Claude in Chrome so that a project's settings files can no longer turn it on; use --chrome, /chrome or your user settings
Open official changelog ↗

Documentation

Documentation excerpt

Allow Claude in Chrome alongside the managed set

By default, when you deploy managed-mcp.json, Claude Code blocks the built-in Claude in Chrome server in terminal sessions. Users don't get the extension install prompt, and a session where the user turned on Chrome by default starts without it and prints no warning. If a user who could otherwise run Claude in Chrome starts claude --chrome, Claude Code exits at startup with an error that names the allowClaudeInChromeWithManagedMcp setting.

To let users run Claude in Chrome alongside the managed set, set "allowClaudeInChromeWithManagedMcp": true in the device's own managed settings. Put it in an MDM-deployed plist, an HKLM registry key, or a system managed-settings.json file, whichever of those Claude Code selects on that device. Requires Claude Code v2.1.282 or later. Claude Code reads the setting only from those device sources, even when server-managed settings deliver the rest of your policy. A deniedMcpServers entry for claude-in-chrome still blocks the server with the setting on.

Documentation snapshot · 2026-11-20

Change details