{"version":"2.1.273","anchor":"tengu-bridge-child-auto-mode-now-defaults-on","canonical_anchor":"tengu-bridge-child-auto-mode-now-defaults-on","heading":"tengu_bridge_child_auto_mode now defaults on","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/tengu-bridge-child-auto-mode-now-defaults-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### tengu_bridge_child_auto_mode now defaults on\n\nThe gate for defaulting bridge-spawned child sessions to Auto mode now compiles to true by default\n\n**What**\n\nWhen the Claude remote-control bridge (which connects the Claude mobile app to a Claude Code session on your computer) spawns a child session, it can default that session to Auto permission mode. The internal flag controlling this default, `tengu_bridge_child_auto_mode`, now compiles to true instead of false. This flag also decides whether the spawn path fetches session tags before starting, and feeds into whether a spawned bridge child receives the `CLAUDE_CODE_BRIDGE_CHILD_AUTO_DEFAULT` setting.\n\n**Why**\n\nThis is a change to the compiled default of an internal flag, not a statement about whether it is switched on for any particular account; whether it actually takes effect depends on server-side rollout.\n\n- Flag `tengu_bridge_child_auto_mode`: Not enough to say (read for one account on one subscription tier against v2.1.273; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Remote Control\n- Names: `CLAUDE_CODE_BRIDGE_CHILD_AUTO_DEFAULT`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}