{"version":"2.1.311","anchor":"trusted-device-check-gains-an-extra-prerequisite-error-befor","canonical_anchor":"trusted-device-check-gains-an-extra-prerequisite-error-befor","heading":"Remote Control runs another check before the Trusted Devices check","tier":"notice","area":"Remote Control","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/trusted-device-check-gains-an-extra-prerequisite-error-befor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Remote Control runs another check before the Trusted Devices check\n\nBefore checking Trusted Devices enrollment, Remote Control now runs another check that can stop it with its own error message\n\n**Unclear.** It is not stated what the new check tests or what its error says.\n\n**What**\n\nRemote Control lets you drive a Claude Code session from another device. Before it starts, Claude Code checks whether its requirements are met, including whether your organization requires Trusted Devices and this device is enrolled. A further check now runs before that one. If it reports a problem, Remote Control stops with that message instead.\n\nThe existing message is unchanged: if your organization requires Trusted Devices and this device is not enrolled, you are asked to run `\/login` to enroll it.\n\n**Why**\n\nRemote Control may refuse to start with an error message different from the Trusted Devices one.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: yes"}