Claude in Chrome decides whether to connect at startup and tells hosts

What

Claude 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:

• 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.
• 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.
• 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.
• Errors: calling a Chrome connection that cannot be reached now raises its own error.

Why

Turning 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.