{"version":"2.1.323","anchor":"memory-sync-tool-in-use-protection-and-delete-mode-changes","canonical_anchor":"memory-sync-tool-in-use-protection-and-delete-mode-changes","heading":"Memory sync no longer overwrites files a tool is still using","tier":"notice","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/memory-sync-tool-in-use-protection-and-delete-mode-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Memory sync no longer overwrites files a tool is still using\n\nMemory sync now skips writing a memory file while a tool is still using it, and warns more plainly when a delete was not sent\n\n**Unclear.** It is not clear what switches the new delete mode on, or whether it is on by default.\n\n**What**\n\nMemory sync keeps Claude's memory files in step across several stores. While it writes, it now holds a guard on the file. If a tool is still using that file, the write is skipped.\n\nOther changes:\n\n- The notice after a pull now says it kept local files that changed or were in use during the pull.\n\n- The check for whether deletions are pushed out has a second way to be switched on.\n\n- When memory sync is not sending changes, its notice warns that a delete has probably not gone out. Before, this warning appeared only when a separate switch was on.\n\n**Why**\n\nMemory files are less likely to be overwritten while in use, and Claude gets a more honest notice when a deletion has not been sent.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}