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
HomeReleasesv2.1.225entry #28

Claude Code v2.1.225 ·

Untrusted-device recovery can be turned off by a flag; unarchive gets its own 403 handling

Untrusted-device failures still recover automatically, and expired trusted-device sessions now tell you to run /login.

You'll notice Notable Improvements
JSON All of v2.1.225
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.225,
What probably matters to youSection of the release
What

Whether an untrusted-device failure counts as auth-recoverable is now controlled by a kill switch, and the 403 classification used by archive and unarchive was split.

Details
  • the recoverability check changed from reason === "untrusted_device" || reason === "session_stale_relogin" to treating untrusted_device as recoverable only when the proactive-enrollment kill switch is off
  • gate is tengu_sessions_elevated_auth_disable_proactive_enrollment, fallback false, so absent a remote value untrusted_device stays recoverable
  • archive and unarchive pass different 403 classification modes; only unarchive maps session_stale_relogin
  • that reason surfaces as "session expired for trusted-device check — run /login to re-authenticate"
Evidence

tengu_sessions_elevated_auth_disable_proactive_enrollment

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundle/login

See this entry in the whole of v2.1.225 →

Feedback