{"version":"2.1.280","anchor":"device-re-enrollment-flow-when-a-device-key-conflict-is-dete","canonical_anchor":"device-re-enrollment-flow-when-a-device-key-conflict-is-dete","heading":"Device re-enrollment flow when a device key conflict is detected","tier":"notice","area":"Device Enrollment","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/device-re-enrollment-flow-when-a-device-key-conflict-is-dete","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Device re-enrollment flow when a device key conflict is detected\n\nClaude Code can now re-register a device when its saved key conflicts with a stored one\n\n**What**\n\nClaude Code links a local computer (a \"device\") to your account by storing a device key. Previously, if that registration failed because a different key was already stored for the device, there was no way to recover. Now Claude Code detects this key conflict and asks you to confirm re-registering the device. If you confirm, it retires the old stored key (retrying that removal a bounded number of times if needed) and then re-binds the device with a new key.\n\n**Why**\n\nThis fixes a dead end: a device whose stored key had gotten out of sync with the account could previously fail to register with no recovery path. A `tengu_device_reenroll` telemetry event records whether you confirmed the re-enrollment, so this new flow can be tracked.\n\n- Area: Device Enrollment\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}