{"version":"2.1.274","anchor":"team-memory-sync-individual-files-can-be-refused-without","canonical_anchor":"team-memory-multi-store-sync-structured-basis-load-failure","heading":"Team memory sync adds scope-aware checks and per-file refusal handling","tier":"notice","area":"Team Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/team-memory-sync-individual-files-can-be-refused-without","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Team memory sync adds scope-aware checks and per-file refusal handling\n\nTeam memory sync now reports why a shared basis failed to load, checks mount-dir escapes per scope, and can skip individually refused files\n\n**Unclear.** Whether the tengu_team_mem_push_delete_deferred or tengu_org_memory_first_write_into_write_home gates are switched on for any account is unread, so nothing can be said about their status.\n\n**What**\n\n- The team-memory sync system now reports a specific reason when it can't load a shared memory basis, such as the store being empty, unreadable, mismatched, or over a size cap, instead of just failing silently.\n\n- A new `account` scope is recognized in several sync checks, for example skipping local-write-preservation checks and allowing pulls even when the walk found nothing.\n\n- The check that stops memory files from being written outside their allowed mount directory (an escape check) is now scope-aware, handling `user`, `account`, and `team` scopes differently through a shared helper.\n\n- If the server refuses to save one particular file during a sync, that file is now marked as refused and skipped on retries for a while, while the rest of the sync continues; the file stays local only and its changes will be lost if the machine is recycled. The sync result reports how many files were refused.\n\n- The internal state Claude Code tracks during a sync now includes fields for refused writes and for whether the shared basis is unusable.\n\n**Why** These changes make multi-device team memory sync more resilient: one problematic file or an unreadable shared store no longer breaks the whole sync, and the system can explain more precisely what went wrong.\n\n- Area: Team Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}