{"version":"2.1.287","anchor":"claude-in-chrome-startup-connect-decision","canonical_anchor":"ide-init-payload-gains-claude-in-chrome-at-startup","heading":"Claude in Chrome decides whether to connect at startup and tells hosts","tier":"notice","area":"Chrome","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/claude-in-chrome-startup-connect-decision","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Claude in Chrome decides whether to connect at startup and tells hosts\n\nA new startup check decides whether Claude in Chrome connects, reported to hosts as `at_startup` and `claude_in_chrome_at_startup`\n\n**Unclear.** It is not clear which sessions run this startup check; one message refers to the editor.\n\n**What**\n\nClaude in Chrome lets Claude work with your Chrome browser. A new startup check now decides whether to connect to it when a session starts, and the answer is passed on to the apps that run Claude Code:\n\n- The check: it connects only if the `claudeInChromeDefaultEnabled` setting (\"Enabled by default\") or `settingOn` is on, your organization's policy allows it, and `CLAUDE_CODE_ENABLE_CFC` is not set to false.\n\n- Status: the Claude in Chrome status now has an optional `at_startup` true or false. Host apps such as the desktop app use it to decide whether to connect open sessions when \"Enabled by default\" is turned on.\n\n- Editors: the reply an editor such as VS Code gets when it starts Claude Code now has an optional `claude_in_chrome_at_startup` field, for editors that connect Claude in Chrome themselves.\n\n- Errors: calling a Chrome connection that cannot be reached now raises its own error.\n\n**Why**\n\nTurning on \"Enabled by default\" can now carry through to editors and the desktop app, so Claude in Chrome may connect automatically at the start of a session where those conditions are met.\n\n- Area: Chrome\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}