{"version":"2.1.247","anchor":"empty-memory-files-are-never-pushed-over-shared-memory","canonical_anchor":"empty-memory-files-are-never-pushed-over-shared-memory","heading":"Empty memory files are never pushed over shared memory","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/empty-memory-files-are-never-pushed-over-shared-memory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Empty memory files are never pushed over shared memory\n\nAn accidentally emptied memory file can no longer wipe your team or org shared memory.\n\n**What**\n\nTeam and org memory sync now skips any memory file that is zero bytes instead of pushing it, so an accidentally emptied file on disk can no longer wipe the shared copy. When the pull side refills such a file, you get a notice explaining that an empty file is never synced over a memory's shared content, and that deleting the file is how you remove a memory.\n\n**Details**\n\n- The push loop compares each file's hash against the hash of empty content, counts the matches, skips them, and logs a warning naming the count.\n- The push result gained an `emptySkipped` count alongside the existing counts for skipped secrets and oversized files.\n- Unconditional on this path; there is no flag to turn it off.\n\n**Evidence**\n\n`emptySkipped`, `an empty file is never synced over a memory's shared content.`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}