{"version":"2.1.238","anchor":"bridge-sessions-refuse-to-start-on-a-device-that-is-not-enro","canonical_anchor":"bridge-sessions-refuse-to-start-on-a-device-that-is-not-enro","heading":"Bridge sessions refuse to start on a device that is not enrolled","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/bridge-sessions-refuse-to-start-on-a-device-that-is-not-enro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Bridge sessions refuse to start on a device that is not enrolled\n\nRemote Control bridge sessions refuse to start unless your device is enrolled as trusted.\n\n**What**\n\nBefore a Remote Control bridge session starts, Claude Code checks that the device is enrolled as a trusted device. If it is not, the session is skipped, the reason is logged, and the failure is reported as either terminal or an auth problem.\n\n**Details**\n\n- The unenrolled case is recorded as `trusted_device_unenrolled`.\n- Runs on the bridge session start path.\n\n**Evidence**\n\n`trusted_device_unenrolled`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}