Claude could be warned when a memory file it read has since changed, but that's off.
Stale-memory update blocks are built behind an internal flag that is off unless server config enables it.
What's wrong with this entry?
New machinery watches memory read and write tool calls and the version stamps on their results. If a memory file the model read earlier has changed since, an update block is injected telling the model its earlier read is stale, with instructions never to quote or paraphrase that block back to you. Gated behind an internal flag that is off unless server config enables it, so nothing in this build turns it on.
- Tracks tool calls matching the memory read, write, string-replace and append tools.
- Freshness is decided by comparing the version stamp seen at read time against the current one.
This memory_read result is stale
Strings lifted out of the shipped bundle, so the claim above can be checked against them.