{"version":"2.1.311","anchor":"chrome-mcp-server-loading-deferred-behind-claude-code-chrome","canonical_anchor":"chrome-mcp-server-loading-deferred-behind-claude-code-chrome","heading":"New setting to load the Claude in Chrome connection later in startup","tier":"use","area":"Claude in Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/chrome-mcp-server-loading-deferred-behind-claude-code-chrome","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### New setting to load the Claude in Chrome connection later in startup\n\nSetting CLAUDE_CODE_CHROME_LATE_MCP_SERVER makes Claude Code skip its early Chrome setup and load the Chrome connection a different way\n\n**Unclear.** It is not clear what the extra internal check requires or how the Chrome connection behaves differently when the variable is set.\n\n**What**\n\nClaude Code can work with the Chrome browser through Claude in Chrome. Part of that is an MCP server, a small helper program that gives Claude Code extra tools, here for controlling the browser.\n\nA new environment variable, `CLAUDE_CODE_CHROME_LATE_MCP_SERVER`, changes how that connection starts. An environment variable is a named value you set in your shell before starting Claude Code. When it is set to true and a further internal check passes, Claude Code skips its usual early Chrome setup step. Claude Code also loads the Chrome connection code from a separate piece of the program. When the variable is not set, Claude Code starts the Chrome connection the same way as before.\n\nIn the same change, the Chrome MCP server and its connection code are now loaded only when needed, rather than always being loaded at startup.\n\n**Why**\n\nThis looks like an experiment to make startup faster when the Chrome integration is in use. It does nothing unless you set the variable.\n\n- Area: Claude in Chrome\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}