Revoked device keys now get a distinct 'device_revoked' reason instead of a silent retry
Device sign-in and sync now recognize a revoked device key as its own failure reason, shown as removed from claude.ai devices, instead of silently retrying
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Device BindingArea: what it touches
ImprovementsKind: in v2.1.277,
ImprovementsSection of the release
What
The device-linking flow used to catch a "device key revoked" error and automatically re-register; that automatic retry has been removed. Registration failures are now classified explicitly, including a new device_revoked reason.
Device-bind failure telemetry now includes a revoked boolean, and the failure outcome gains a device_revoked case, shown to users as "removed from claude.ai devices," alongside the existing limit_reached, registration_unavailable, and no_keychain reasons.
The local-tools/file-sync messages shown when a session is unbound now special-case device_revoked with its own explanation, instead of showing the generic sync-error text.
Why
Users who've had a device removed from claude.ai now see a clear, specific explanation instead of a silent, potentially confusing automatic retry or a generic sync error.
