Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

Mass-delete guard check across multiple memory stores, no confirmed caller in my slice

New guard checks for mass-deletion across multiple memory stores at once, not yet confirmed to be in use

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

A new internal function checks a list of memory stores together, applying the same threshold used elsewhere to detect when too many files appear to have been deleted from a single store, but now across the whole set of stores at once. It reports back the threshold used, how many files are missing, and how many targets remain on disk.

Why

This appears to be a safety check meant to catch large-scale accidental deletion spanning multiple memory stores, though it isn't confirmed where or when it is actually called.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtNo confirmed caller for this function was found, so it's unclear when or whether it currently runs.

See this entry in the whole of v2.1.280 →

Feedback