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 #62

Claude Code v2.1.225 ·

Code-session failures are now a terminal/non-terminal discriminated union

Expired logins during code sessions now refresh and retry automatically instead of failing the operation.

You'll notice 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,
ImprovementsSection of the release
What

HTTP failures from code-session calls are classified in one place, and a 401 is treated as recoverable so the caller refreshes OAuth and retries instead of failing the operation.

Details
  • one helper returns "oauth_rejected" for 401, "transient" for 408, 429 and any status >= 500, and "rejected" otherwise
  • 401 yields { terminal: !1, reason: "oauth_rejected" }
  • the type guards now check e.terminal === !0 / e.terminal === !1 rather than testing for the presence of a terminal key
  • the bridge's 401 retry path also fires when the result is any non-terminal failure
Evidence

oauth_rejected

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

See this entry in the whole of v2.1.225 →

Feedback