{"version":"2.1.271","anchor":"chrome-mcp-server-now-loads-cloud-gateway-sign-in-at-startup","canonical_anchor":"chrome-mcp-server-now-loads-cloud-gateway-sign-in-at-startup","heading":"Chrome MCP server now loads Cloud gateway sign-in at startup with graceful fallback","tier":"internal","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/chrome-mcp-server-now-loads-cloud-gateway-sign-in-at-startup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Chrome MCP server now loads Cloud gateway sign-in at startup with graceful fallback\n\nThe Chrome MCP server now tries to sign in to the Cloud gateway at startup and falls back gracefully if that fails\n\n**What**\n\nThe `claude-in-chrome` MCP server (the background service that lets Claude Code control Chrome) now attempts to load its Cloud gateway sign-in as soon as it starts. If that attempt fails, it logs a warning and keeps running as if it were never signed in to the gateway, until the server is restarted.\n\n**Why**\n\nThis makes a gateway sign-in failure visible and predictable instead of failing silently or behaving inconsistently. If Chrome-based tools seem to be missing gateway access, restarting the server is the way to retry the sign-in.\n\n- Area: Chrome & Browser\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}