Unclear How Claude Code decides that a session counts as remote or Cowork is not shown.
What
The check that decides whether Claude Code connects to Claude in Chrome when it starts now ignores two settings it used to follow:
- In remote and Cowork sessions,
claudeInChromeDefaultEnabledis now ignored and Chrome is not connected. In these sessions Chrome connects at startup only if you start with--chromeor withCLAUDE_CODE_ENABLE_CFC=1set in the startup environment. Before, the setting was used whenever it was defined. - If a project's settings file sets
CLAUDE_CODE_ENABLE_CFCin itsenvblock, Claude Code now ignores it. At startup it warns that a project can't turn on Claude in Chrome and tells you to run/chromeor start with--chrometo turn it on yourself.
The Chrome setup notification also has new text: "Claude in Chrome", with "Set up Claude in Chrome so this task can use your browser".
Why
A project you open can no longer switch on browser control for you without asking. If you had Claude in Chrome on by default, it now stays off in remote and Cowork sessions unless you turn it on with --chrome or CLAUDE_CODE_ENABLE_CFC=1.
Names in the bundleclaudeInChromeDefaultEnabled
Documented inclaude-code/settings-reference
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
How Claude Code decides that a session counts as remote or Cowork is not shown.
Anthropic's release notes agree
Changed Claude in Chrome so that a project's settings files can no longer turn it on; use --chrome, /chrome or your user settings