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

Bridge recovery for expired worker credentials on close code 4094

You'll notice
Useful3 Signal0
Remote Control

When your remote worker credential expires, the bridge now re-mints it and refreshes login instead of dying.

What

The remote bridge can now recover from a worker credential expiry instead of just reporting the close code, re-minting the credential and forcing an OAuth refresh.

Details
  • Adds a recovery-table entry for close code 4094 alongside the existing 401, 4091 and 4093 entries.
  • The 4094 entry re-mints the worker credential and sets needsOAuthRefresh: !0.
  • Epoch-mismatch conditions token_expired and auth_exhausted map to 4094.
  • Gated on the typed close-code mapping, passed as causeTypedCloseCodes: !0 by both bridge callers, so it is active for the remote bridge.
  • The plain "code 4094" close-reason text existed in 2.1.224; only the recovery handling is new.
Evidence

worker credential expired \u2014 re-minting

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 →