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.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

Remote worker heartbeats can adopt refreshed credentials

Under the hood
Useful2 Signal0
Sessions Notable not in their notes

Long-running remote sessions can pick up refreshed tokens mid-flight instead of dying when credentials expire.

CLAUDE_CODE_REMOTE
What

A heartbeat response can now carry a refreshed auth payload, letting a long-running remote worker pick up new tokens without a restart.

Details
  • On receiving the payload the client re-reads the session ingress token and OAuth token from disk.
  • Adoption only happens if the new token decodes as a JWT, its expiry matches the advertised lifetime, and it extends the current expiry.
  • Each non-adoption reason is reported once: not_remote, no_advertised_ttl, read_failed, not_a_jwt, unchanged, exp_mismatch, not_newer, adopt_timeout, adopt_threw.
  • The heartbeat request timeout is now derived from the heartbeat interval and jitter rather than a fixed 5000 ms.
  • Gated on the CLAUDE_CODE_REMOTE environment; non-remote sessions report not_remote and keep existing credentials.
Evidence

CCR auth refresh: delivered token does not extend expiry, keeping current credentials

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