{"version":"2.1.281","anchor":"remote-control-bridge-records-how-it-was-enabled-systemini","canonical_anchor":"remote-control-bridge-records-how-it-was-enabled-systemini","heading":"Remote Control bridge records how it was enabled; system\/init re-sends on a new value","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-control-bridge-records-how-it-was-enabled-systemini","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote Control bridge records how it was enabled; system\/init re-sends on a new value\n\nRemote Control now records whether it was turned on explicitly, by default or by a setting, and re-sends session info when a new value changes\n\n**Unclear.** The finding does not say what the newly watched value is.\n\n**What**\n\nRemote Control lets a session be driven from another device. When it starts up, Claude Code now records how it was turned on:\n\n- \"explicit\", when it was switched on directly.\n\n- \"auto_default\", when it came on by default through `replBridgeAutoOnByDefault`.\n\n- \"auto_settings\", when a setting turned it on.\n\nThe setup also watches a new value. When that value changes, Claude Code sends a fresh system\/init message over the bridge. That message describes the session to the connected side.\n\n**Why**\n\nClaude Code can now tell a deliberate Remote Control start apart from an automatic one. The connected side also gets updated session details when the new value changes."}