Source Intelligence

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

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

You'll notice
Useful3 Signal0
Auth

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

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.

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 →