{"version":"2.1.129","anchor":"trusted-device-enrollment-for-remote-control","canonical_anchor":"trusted-device-enrollment-for-remote-control","heading":"Trusted Device Enrollment for Remote Control","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.129\/e\/trusted-device-enrollment-for-remote-control","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.129","markdown":"### Trusted Device Enrollment for Remote Control\n\n**What**\n\nRemote Control now has a first-run enrollment path for organizations that require Trusted Devices.\n\n**Usage**\n\n`claude remote-control # or inside a session: \/remote-control` **Details** - If Remote Control preflight finds that the device must be enrolled, Claude Code starts a sign-in flow instead of only reporting that the device is blocked. - If sign-in is canceled or enrollment does not complete, Claude Code now gives specific next steps. - Organizations can temporarily disable proactive enrollment with a feature flag, in which case users see an explicit administrator-facing message. **Evidence** Trusted Device enrollment flow (search for `\"Sign in to enroll this device for Remote Control.\"` and `\"Your organization requires Trusted Devices for Remote Control, but enrollment is temporarily disabled\"`)"}