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

Update manifest fetches retry when the connection drops

You'll notice
Useful2 Signal1
Updater

Update checks retry when the connection drops instead of failing the whole check.

What

The native updater's manifest request, which uses a 10 second timeout and expects JSON, now retries on a dropped connection up to the shared retry limit with a 1 second pause between attempts, instead of failing the update check outright.

Details
  • The outcome reports whether a manifest retry happened, alongside the existing flag for the download's own drop-retry.
  • Unconditional in the native updater; no setting involved.
Evidence

Manifest fetch connection dropped on attempt

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 →