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.223 Home All releases ←olderv2.1.222 v2.1.224newer→
Claude Code v2.1.223

Daemon lock and auto-update lock gained storage-backend implementations

Under the hood
Useful1 Signal0
Storage Backend

Lock files that stop two sessions clashing can now live in a storage backend instead of on disk.

What

Acquiring, reading, replacing and releasing the daemon lock, plus the auto-updater's stale-lock detection and release, now each have a storage-key branch alongside the original file-based logic.

Details
  • acquisition uses an ifAbsent write with a umask-derived mode; staleness is decided from stat; release deletes the key
  • lock-contention telemetry codes trigger a re-read and one retry before the acquisition fails
  • the file-based path is still present and is what runs without a backend
Evidence

[DaemonLock] Failed to acquire daemon lock:

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