{"version":"2.1.225","anchor":"cloud-and-remote-sessions-try-to-start-device-registration","canonical_anchor":"cloud-and-remote-sessions-try-to-start-device-registration","heading":"Cloud and remote sessions try to start device registration","tier":"soon","area":"Device Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/cloud-and-remote-sessions-try-to-start-device-registration","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Cloud and remote sessions try to start device registration\n\nCloud and remote sessions try to start device registration, which does nothing while the gate is off.\n\n**What**\n\nAttaching a cloud session and completing remote auth setup both now attempt to bring up the device bridge for that session.\n\n**Details**\n\n- both paths dynamically import `startDeviceRegistration` and call it with the session id, an access-token getter and the org uuid\n- registration short-circuits on its own enable and egress checks, so nothing happens unless `tengu_violin_wood` and the `allow_remote_sessions` policy both permit it\n\n**Evidence**\n\n`startDeviceRegistration`\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.225; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) 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: Device Bridge\n- Names: `allow_remote_sessions`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}