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
Home / Reference / Settings keys

claudeInChromeDefaultEnabled

setting never mined documented JSON

A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

Turn on Chrome integration when a session starts, in the interactive CLI and the VS Code extension

Anthropic's own wording. Read off All settings, captured 2026-10-02.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 131on this box, as of v2.1.288
Written about v2.1.280 first named in a changelog, 22 Sep 2026

In the changelogs

4

Releases whose published page names claudeInChromeDefaultEnabled.

  1. v2.1.287
    IDE extensions can be told to connect Claude in Chrome when a session starts

    Claude Code now tells an IDE that connects Claude in Chrome itself whether to connect it at session start

    named in this entry, found in this entry's text

  2. v2.1.287
    Claude in Chrome has a new check deciding whether it connects at startup

    Claude Code now decides at startup whether to connect to Claude in Chrome, based on a setting, your organization's policy and CLAUDE_CODE_ENABLE_CFC

    found in this entry's text

  3. v2.1.280
    Three new hidden CLI settings-edit commands for the VS Code extension

    Three new hidden CLI commands let the VS Code extension edit skill, sandbox, and Chrome settings

    found in this entry's text

  4. v2.1.280
    Claude in Chrome status telemetry function added

    Added a telemetry function that reports Claude in Chrome's extension pairing and connection status

    found in this entry's text

First cited

2

The earliest release whose published evidence quoted claudeInChromeDefaultEnabled was v2.1.280, 22 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.28022 Sep 2026enabled_by_default: o.claudeInChromeDefaultEnabled ?? !1
v2.1.2871 Oct 2026at_startup: await i(o.claudeInChromeDefaultEnabled === !0)

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.

Feedback