Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.224 ·

New memory_write tool for saving documents to a connected memory store

Claude can now save documents into a connected memory store, with secret scanning blocking risky writes.

Use it now Notable New Features
JSON All of v2.1.224
Use it nowTier: how much it should matter to you
5Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
MemoryArea: what it touches
New FeaturesKind: in v2.1.224,
What probably matters to youSection of the release
What

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.

Details
  • 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.
Evidence

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.

Read from
Names in the bundlememory_writememory_listmemory_readCLAUDE_MEMORY_STORESCLAUDE_CODE_DISABLE_ORG_MEMORY
Feature flag
tengu_haze_glass Off in both readings

The 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: off

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 has happened since
Flag reading moved The flag server now returns off for tengu_haze_glass, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_haze_glass, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.224 →

Feedback