You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MemoryArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
What
Memory sync has three states: "open", "held" and "closed". Your organization can allow or disallow it through a managed setting called allow_memory_sync.
Before, when the organization disallowed it, memory sync was treated as not set up at all. Now it still counts as set up, and its state is "closed".
Why
This lets Claude Code tell apart "memory sync is not set up" from "memory sync is set up but your organization has blocked it", which parts of Claude Code that check for the closed state can now act on.
Read from
Names in the bundleallow_memory_sync
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what a user sees differently when memory sync is blocked by the organization.
Anthropic's release notes agreeImproved screen-reader output in /mcp: a disabled server is read as "off" instead of "pending"
