Unclear Whether this is enabled for any accounts is unknown, since the related gate tengu_bridge_child_machine_settings is unread.
What
- When Claude Code spawns a Remote Control bridge worker child process, it can now set a new environment variable,
CLAUDE_CODE_BRIDGE_CHILD_MACHINE_SETTINGS="1", alongside the existingCLAUDE_CODE_BRIDGE_CHILD_AUTO_DEFAULTandCLAUDE_CODE_BRIDGE_CHILD_ARTIFACTvariables. This is set for project-thread child sessions when a related feature flag is on. - When this bridge-child machine-settings mode is active, Claude-in-Chrome (the browser integration, referred to as CFC) is no longer turned on by default in cases where it otherwise would be.
Why
This lets bridge child sessions run with their own machine-level settings without unexpectedly also turning on the Chrome browser integration by default.
tengu_bridge_child_machine_settings Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.273: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.273. It isn't a statement about your account. What a flag value here can and cannot tell you
Whether this is enabled for any accounts is unknown, since the related gate `tengu_bridge_child_machine_settings` is unread.
New in this build: CLAUDE_CODE_BRIDGE_CHILD_MACHINE_SETTINGS