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.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Stale background worker rosters no longer trigger upgrade respawns

Under the hood
Useful2 Signal2
Background Daemon

A returning background supervisor ignores stale worker lists instead of respawning them.

What

When the background supervisor comes back after being down, it checks how old the previous list of workers is. If it is old, it skips the pending upgrade respawns for those workers, and they no longer count toward the "all workers dead" health verdict.

Details
  • The adopt log line reports the roster's age in days and how many respawns were skipped.
  • Settling a worker can now come back as dead-epoch, and the adoption telemetry event gained dead-epoch and upgrade-skipped counters.
Evidence

upgrade_skipped=${me} (previous roster written ${Math.round((Date.now() - M.updatedAt) / 86400000)}d ago)

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