Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.287 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.287 ·

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

A new startup check decides whether Claude in Chrome connects, reported to hosts as at_startup and claude_in_chrome_at_startup

Group of 3 You'll notice Improvements
JSON All of v2.1.287
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ChromeArea: what it touches
ImprovementsKind: in v2.1.287,
ImprovementsSection of the release

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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which sessions run this startup check; one message refers to the editor.

See this entry in the whole of v2.1.287 →

Feedback