{"version":"2.1.275","anchor":"team-memory-multistore-conflict-telemetry-no-longer-fires-fo","canonical_anchor":"team-memory-multistore-conflict-telemetry-no-longer-fires-fo","heading":"Team-memory multistore-conflict telemetry no longer fires for account-scope stores","tier":"internal","area":"Team Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/team-memory-multistore-conflict-telemetry-no-longer-fires-fo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Team-memory multistore-conflict telemetry no longer fires for account-scope stores\n\nTeam-memory conflict warnings no longer fire for account-scoped memory stores\n\n**What**\n\nClaude Code's team-memory feature logs a `team_memory_multistore_conflict` event when it detects certain conflicts, such as a manifest changing mid-pull, a manifest appearing foreign at write time, an unlisted non-empty directory, or a foreign partition directory. These checks now skip firing when the memory store in question is scoped to the account rather than to a team.\n\n**Why**\n\nThis avoids raising multistore-conflict warnings for memory stores that are personal to an account, where that kind of conflict isn't meaningful, reserving the warning for cases where it actually indicates a problem.\n\n- Area: Team Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}