{"version":"2.1.318","anchor":"shared-team-memory-sync-handles-named-removals-and-held-back","canonical_anchor":"shared-team-memory-sync-handles-named-removals-and-held-back","heading":"Shared team memory sync now handles removed and held-back files","tier":"notice","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/shared-team-memory-sync-handles-named-removals-and-held-back","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Shared team memory sync now handles removed and held-back files\n\nWhen pulling shared team memory, Claude Code now skips writing held-back files and replays recorded removals before writing a conflict notice\n\n**What**\n\nShared team memory is a set of notes shared between members of a team. When Claude Code pulls it down, it now does two things differently:\n\n- it skips writing files on a held-back list\n\n- it replays removals that were recorded by name before it writes a notice about a conflict\n\nThe notice about deleted files can also use different wording when an internal check is on.\n\n**Why**\n\nThis changes how conflicts in shared team memory are settled, so files someone deliberately removed are less likely to reappear.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}