{"version":"2.1.277","anchor":"device-bind-elevated-tier-ask-flow-gated-behind-an-unresol","canonical_anchor":"device-binding-now-retries-registration-on-a-stale-device-ro","heading":"Device registration now retries and can force a re-learn on stale or revoked device rows","tier":"notice","area":"Device Binding","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/device-bind-elevated-tier-ask-flow-gated-behind-an-unresol","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Device registration now retries and can force a re-learn on stale or revoked device rows\n\nDevice binding\/registration gained a re-learn path and automatic retry when the server no longer recognizes the current device\n\n**What**\n\n- Device registration now accepts a `relearn` flag that skips the cached row and re-registers the device even when a cached `deviceUUID` already exists.\n\n- An HTTP 409 (or a specific error code) combined with a `revoked_at` timestamp is now treated as its own \"already exists \/ relearn needed\" condition, with a dedicated error class, instead of being treated as a generic revoked-key error.\n\n- The device-bind flow, which cryptographically binds a session to a device, now retries automatically: if the server refuses a signed create with a 404 against the currently-registered device, the client calls `reregister()` and retries the signed create once with the new device identity, instead of giving up unbound.\n\n- Session creation can also now ask the server for an \"elevated\" security tier when binding a device, controlled by a feature flag and an organization policy-enforcement check.\n\n**Why**\n\nThese changes make device binding more resilient when a device's registration has expired, been revoked, or gone stale on the server, letting sessions recover automatically instead of falling back to a less-trusted, unbound state.\n\n- Flag `tengu_breezy_fairy`: Off in both readings (read for one account on one subscription tier against v2.1.277; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Device Binding\n- Names: `tengu_breezy_fairy`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}