{"version":"2.1.273","anchor":"bridge-child-now-told-about-permission-mode-changes-even-be","canonical_anchor":"bridge-child-now-told-about-permission-mode-changes-even-be","heading":"Bridge child now told about permission-mode changes, even before it's mounted","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/bridge-child-now-told-about-permission-mode-changes-even-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Bridge child now told about permission-mode changes, even before it's mounted\n\nPermission-mode changes are now buffered and delivered to the remote-control bridge even before it's connected\n\n**What**\n\nWhen the permission mode changes during a session, a new helper now forwards that change to the bridge child session (used for remote control \/ mirroring) via `noteModeChoice`. If the bridge child isn't mounted yet at the time of the change, the mode choice is now held onto and delivered once the bridge child does mount, instead of being lost.\n\n**Why**\n\nThis prevents a permission-mode change from being silently dropped when it happens before a remote-control connection is fully set up, so remote sessions stay in sync with the actual permission mode.\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- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}