{"version":"2.1.299","anchor":"trusted-device-re-enrollment-guarded-after-a-403","canonical_anchor":"trusted-device-re-enrollment-guarded-after-a-403","heading":"No more repeated trusted-device enrollment after this computer is refused","tier":"notice","area":"Auth","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/trusted-device-re-enrollment-guarded-after-a-403","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### No more repeated trusted-device enrollment after this computer is refused\n\nAfter a trusted-device refusal, Claude Code renews enrollment once and stops looping if the renewed device is still refused\n\n**What**\n\nSome accounts require the computer to be enrolled as a trusted device. When the server refuses this computer as untrusted, Claude Code now behaves like this:\n\n- It renews the trusted-device enrollment and retries once.\n\n- If the server still refuses, it shows a message saying it still refused this computer after the enrollment was renewed.\n\n- If the refused device token came from an enrollment made after an earlier refusal, it does not enroll again until a sign-in clears it.\n\n- If the saved time of the last enrollment is unusable, it skips enrolling.\n\nBefore, it enrolled again whenever a waiting period had passed.\n\n**Why**\n\nThis stops Claude Code from getting stuck enrolling the same computer over and over. If you see the new message, signing in again is what clears it.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}