Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

New device re-enrollment flow for revoked or invalid device credentials

A new device re-enrollment dialog, telemetry kind, and richer revocation error support recovering from an invalidated device registration.

Group of 3 You'll notice New Features
JSON All of v2.1.280
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Device EnrollmentArea: what it touches
New FeaturesKind: in v2.1.280,
New FeaturesSection of the release

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.

What

  • 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.
  • 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).
  • 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.

Why

This 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt's not confirmed what triggers this dialog or exactly what re-enrollment flow it walks the user through, since only the component's…

See this entry in the whole of v2.1.280 →

Feedback