{"version":"2.1.304","anchor":"auto-mode-can-add-a-chrome-mcp-rule-line-for-remote-browser","canonical_anchor":"auto-mode-can-add-a-chrome-mcp-rule-line-for-remote-browser","heading":"Auto mode can get an extra rule for Chrome browser tools in remote sessions","tier":"internal","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/auto-mode-can-add-a-chrome-mcp-rule-line-for-remote-browser","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Auto mode can get an extra rule for Chrome browser tools in remote sessions\n\nAuto mode can add a Chrome-MCP rule for Claude in Chrome tools when CLAUDE_CODE_AUTO_MODE_REMOTE_BROWSER is set or a remote setting allows it\n\n**What**\n\nAuto mode lets Claude Code decide on its own whether actions are safe to run. It can now add an extra rule line, starting \"- **Chrome-MCP**:\", to the instructions it uses for that decision. The text comes from a remotely supplied setting. MCP (Model Context Protocol) is the way Claude Code connects to outside tools.\n\nThe line is added only when both of these hold:\n\n- The browser tools come from the Claude in Chrome server.\n\n- The environment variable `CLAUDE_CODE_AUTO_MODE_REMOTE_BROWSER` is set, or the remote setting allows it.\n\nThe text is checked before use. It must start with \"- **\", use only printable plain characters, and contain no `<` or backslash.\n\n**Why**\n\nThis changes what auto mode is told about browser tools in cloud sessions, which can affect which browser actions it lets through.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}