Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.225entry #38

Claude Code v2.1.225 ·

Bridge recovery for expired worker credentials on close code 4094

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

You'll notice New Features
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
Remote ControlArea: what it touches
New FeaturesKind: in v2.1.225,
New FeaturesSection of the release
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.

See this entry in the whole of v2.1.225 →

Feedback