Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.219 Home All releases ←olderv2.1.218 v2.1.220newer→
Claude Code v2.1.219

Team-memory mount conflicts fail closed on write and recover automatically

You'll notice
Useful3 Signal0
Team Memory

Shared team memory mounts stop clobbering each other and switch back on once a conflict clears.

What

Writing a store manifest into a shared mount is now race-safe, and a mount suppressed for a conflicting manifest re-enables itself once the conflict is gone.

Details
  • Manifest writes into an absent non-user mount stage to a temp file and hard-link into place, so a racing store cannot be overwritten.
  • Finding another store's manifest at write time throws rather than proceeding.
  • Mounts suppressed as mount_dir_foreign_partition or mount_dir_unmanifested_nonempty are re-adopted automatically, emitting tengu_team_mem_foreign_partition_recovered.
  • Write-time guidance strings were rewritten to name the conflicting directory and state that sync re-enables itself.
Evidence

mount dir holds another store's .memory-sync manifest at write time (fail closed)

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.219 →