{"version":"2.1.285","anchor":"trusted-device-403-handling-reworked","canonical_anchor":"trusted-device-403-handling-reworked","heading":"Remote Control only re-registers your device when the refusal is about trust","tier":"notice","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/trusted-device-403-handling-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Remote Control only re-registers your device when the refusal is about trust\n\nWhen the sessions server refuses Remote Control, Claude Code reads the reason and only re-registers the device if it is untrusted\n\n**What**\n\nA 403 is the server's way of refusing a request. When the sessions server refuses a Remote Control request this way, Claude Code now reads the reason it gave. The reason can be one of these:\n\n- `untrusted_device`: the device is not trusted\n\n- `session_stale_relogin`: the session is out of date and needs you to log in again\n\nClaude Code now tries to recover the device's credentials only when the reason is an untrusted device. Before, it re-registered the device after any 403. The wait between reconnect attempts is also calculated differently.\n\n**Why**\n\nThis changes how Remote Control reconnects and recovers from sign-in problems. A refusal that needs a fresh login no longer sets off a device re-registration that could not fix it.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}