Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.225 Home All releases ←olderv2.1.224 v2.1.226newer→
Claude Code v2.1.225

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

You'll notice
Useful3 Signal0
Auth Notable

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

/login
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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.225 →