Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Team MemoryArea: what it touches
Internal ChangesKind: in v2.1.275,
Internal ChangesSection of the release
What
Claude 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.
Why
This 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.
