Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.219entry #93

Claude Code v2.1.219 ·

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

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

You'll notice Bug Fixes
JSON All of v2.1.219
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Team MemoryArea: what it touches
Bug FixesKind: in v2.1.219,
Bug FixesSection of the release
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.

See this entry in the whole of v2.1.219 →

Feedback