Follow Discord
Sweep 23 Oct 2026 · 21:48Z Build v2.1.310 529 read Stable v2.1.308 Latest v2.1.310 Next v2.1.310 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.242 ·

Auto-update checks are throttled within a long-running process

Long-running sessions stop making redundant auto-update checks; there is no flag for it.

You'll notice Improvements
JSON All of v2.1.242
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
UpdaterArea: what it touches
ImprovementsKind: in v2.1.242,
ImprovementsSection of the release
What

An auto-update check is now skipped if one ran recently, so a long-lived session stops making redundant checks. The skip is logged with how many seconds ago the last check ran. There is no flag.

Details
  • Updater state (time of the last auto-update check, an update-restore failure marker, and minted preserved inodes) moved from module-level globals into one per-process object.
  • The self-heal paths that restore a missing claude binary from a preserved <exe>.old.<timestamp> copy now receive that state explicitly instead of reading globals.
  • The npm install and uninstall shell-outs now resolve the home directory through a helper rather than calling os.homedir() directly.
Evidence

auto-update check throttled (last check

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

Feedback