Device binding/registration gained a re-learn path and automatic retry when the server no longer recognizes the current device
What
- Device registration now accepts a
relearnflag that skips the cached row and re-registers the device even when a cacheddeviceUUIDalready exists. - An HTTP 409 (or a specific error code) combined with a
revoked_attimestamp 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. - 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. - 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.
Why
These 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.
tengu_breezy_fairy Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.277: 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.
Read once, for one account on one subscription tier, against v2.1.277. It isn't a statement about your account. What a flag value here can and cannot tell you