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

Claude Code v2.1.219 ·

Team memory mounts can un-suppress themselves

A memory mount that got suppressed can now recover on the next sync instead of staying stuck until restart.

You'll notice In Development
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
Org MemoryArea: what it touches
In DevelopmentKind: in v2.1.219,
In DevelopmentSection of the release
What

Two suppression reasons on multi-store memory sync are now recoverable instead of sticking until restart.

Details
  • Applies to mount_dir_foreign_partition and mount_dir_unmanifested_nonempty
  • On the next sync the mount dir is re-examined; if the partition now matches or the dir is empty, suppression is cleared with the log "condition cleared — re-adopting the mount dir" and failure counters reset
  • In the same area the separate pushSuppressedReason field is gone entirely, so pushes and periodic resync are no longer gated on it and per-mount suppression is the single mechanism
  • Gating of team memory sync itself was not examined
Evidence

condition cleared — re-adopting the mount dir

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