Claude can now save documents into a connected memory store, with secret scanning blocking risky writes.
tengu_haze_glass Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.224: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.224. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Memory goes from read-only to read-write. Alongside memory_list and memory_read, Claude can now create or overwrite a whole document in a connected, writable memory store, and is prompted to check each of your replies for corrections and preferences worth keeping. Writes are refused for read-only stores, empty content, content over the byte cap, or anything a secret scan flags. Requires memory stores to be connected via CLAUDE_MEMORY_STORES, the allow_memory_sync permission, and CLAUDE_CODE_DISABLE_ORG_MEMORY unset.
- Prompt guidance: one topic per file, frontmatter on each document, and a per-store index document kept current.
- Read-only stores refuse with "The memory store ... is read-only in this session; changes will not persist." Store resolution gained a write flag defaulting to false, which drives that refusal.
- Secret-detection refusal notes the store "is shared across the organization's connected projects."
- Written text is sanitised: control characters become U+FFFD, and line separators including U+2028 and U+2029 become plain newlines.
- The whole feature also sits behind the remote-config flag
tengu_haze_glass, whose fallback in this build is off, so the real value comes from server config. - In auto mode a write is routed to classifier review ("Saving a shared memory document requires classifier review."); in plan mode it asks.
The memory store ${JZo(e)} is read-only in this session; changes will not persist., save a document to a connected project memory store
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.
-
v2.1.223
Read-only org memory tools: memory_list and memory_read
Both mention list read store disable
-
v2.1.219
Org memory: discovery telemetry and store-picker copy
Both mention store disable
-
v2.1.223
Org-memory gating consolidated into one predicate
Both mention read disable