{"version":"2.1.280","anchor":"memory-sync-now-caps-mass-deletion-of-synced-files","canonical_anchor":"memory-sync-now-caps-mass-deletion-of-synced-files","heading":"Bash and memory sync now block bulk deletion of synced memory files","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/memory-sync-now-caps-mass-deletion-of-synced-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Bash and memory sync now block bulk deletion of synced memory files\n\nA new safety cap stops commands from mass-deleting synced memory files at once, asking you to wait for sync to catch up instead\n\n**What**\n\n- A new check (`massDeleteHoldExposure`) blocks removing memory files when doing so would exceed a threshold of missing-or-targeted synced files at once, returning a refusal message that asks you to wait about a minute for sync to catch up.\n\n- A new method on the memory-store manager computes this \"hold exposure\" across both the shared multi-store and the user multi-store whenever a mass delete is requested.\n\n- The Bash tool's input validation now also runs this check asynchronously, after its existing checks, as part of deciding whether a command is allowed.\n\n- Specifically, Bash's validation scans `rm` commands for literal delete targets and calls this memory-store check; if a command would remove more synced memory files than the threshold allows at once, it's refused with an explanatory error instead of being allowed to run.\n\n**Why**\n\nThis prevents a single `rm` command (or other mass-delete action) from wiping out more synced memory files than the sync process can safely account for, avoiding data loss or inconsistent state while sync catches up.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}