{"version":"2.1.273","anchor":"claude-in-chrome-default-enable-now-skipped-when-bridge-chil","canonical_anchor":"claude-in-chrome-default-enable-now-skipped-when-bridge-chil","heading":"Bridge child processes get a machine-settings mode","tier":"notice","area":"Chrome","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/claude-in-chrome-default-enable-now-skipped-when-bridge-chil","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Bridge child processes get a machine-settings mode\n\nRemote Control bridge worker child processes can now run in a machine-settings mode that also changes Claude-in-Chrome defaults\n\n**What**\n\n- 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 existing `CLAUDE_CODE_BRIDGE_CHILD_AUTO_DEFAULT` and `CLAUDE_CODE_BRIDGE_CHILD_ARTIFACT` variables. This is set for project-thread child sessions when a related feature flag is on.\n\n- 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.\n\n**Why**\n\nThis lets bridge child sessions run with their own machine-level settings without unexpectedly also turning on the Chrome browser integration by default.\n\n- Area: Chrome\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}