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.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Workload identity token refresh can proceed without the cross-process lock

Under the hood
Useful2 Signal2
Auth

Workload identity token refresh can now go ahead without the cross-process lock rather than failing.

What

The lock that serializes OAuth refreshes for workload identity federation now has two modes. Fail-closed retries acquisition 5 times; fail-open retries 15 and, if it still cannot get the lock, refreshes anyway without cross-process serialization rather than failing the refresh.

Details
  • The fail-open path logs a debug line explaining that it proceeded unlocked.
  • The existing lock acquire and release telemetry now records which mode was in use.
  • The mode is chosen per call site, not by a user setting.
  • Workload identity client state (the credentials promise, token cache, resolved base URL and failed access tokens) moved from module globals into a resettable object.
Evidence

wif: credentials lock unavailable at

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.242 →