{"version":"2.1.280","anchor":"new-devicereenrolldialog-lazy-loaded-ui-flow","canonical_anchor":"new-devicereenrolldialog-lazy-loaded-ui-flow","heading":"New device re-enrollment flow for revoked or invalid device credentials","tier":"notice","area":"Device Enrollment","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-devicereenrolldialog-lazy-loaded-ui-flow","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New device re-enrollment flow for revoked or invalid device credentials\n\nA new device re-enrollment dialog, telemetry kind, and richer revocation error support recovering from an invalidated device registration.\n\n**Unclear.** It's not confirmed what triggers this dialog or exactly what re-enrollment flow it walks the user through, since only the component's existence and loading pattern are evidenced.\n\n**What**\n\n- A new `DeviceReenrollDialog` component is now lazily loaded and shown using the same pattern as other auth\/session dialogs, prompting the user to re-enroll their device when its credentials have expired or been invalidated.\n\n- A new `device_reenroll` telemetry\/operation kind was added alongside the existing device-related kinds (`device_key_store`, `device_mcp_host_consent`, `device_mcp_serving`, `device_registry_register`).\n\n- When device registration is found to be revoked, the thrown error now includes the device's public key (SPKI, base64-encoded) as `refusedPublicKey`, instead of a bare error with no details.\n\n**Why**\n\nThis gives Claude Code a way to detect a revoked or invalid device registration, tell the user what happened, and walk them through re-enrolling the device instead of failing silently.\n\n- Area: Device Enrollment\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}