Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.228 ·

Lock contention is now a distinct prompt-history write failure

Prompt-history saves blocked by another process are now tracked separately from real write failures.

Under the hood Internal Changes
JSON All of v2.1.228
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.228,
Internal ChangesSection of the release
What

When saving prompt history fails because another process held the lock, it is reported under its own key rather than counted as a generic write failure.

Details
  • Detected from the error's telemetry code being lock-contended or lock-acquire-failed; the distinct key is history_save_lock_failed.
Evidence

history_save_lock_failed

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

Feedback