{"version":"2.1.290","anchor":"device-bridge-enablement-takes-a-cloudclient","canonical_anchor":"device-bridge-enablement-takes-a-cloudclient","heading":"Internal changes to how the device bridge checks it is enabled","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/device-bridge-enablement-takes-a-cloudclient","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Internal changes to how the device bridge checks it is enabled\n\nThe device bridge now checks whether it is enabled through a cloud connection, and more of its stages are recorded in usage data\n\n**Unclear.** It is not clear what the device bridge does for a user or whether this changes anything they would notice.\n\n**What**\n\nThe checks that decide whether the device bridge is enabled, and whether it is still enabled, now go through a cloud client that is passed in to them. Claude Code also records more named stages of this work in its usage data, such as handing off a turn and checking a repository's git state.\n\n**Why**\n\nThese are mostly internal changes, with nothing new to do for most users.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}