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 24 Jul 2026

Team memory mounts can un-suppress themselves

You'll notice

Useful3 Signal0

Org Memory

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

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 →