Rewritten memory rules would make Claude save corrections and environment quirks immediately, before replying.
The new memory system prompt with must-save triggers is gated on tengu_stone_shell, which falls back to false.
tengu_stone_shell 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.219: 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.219. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The memory instructions given to Claude were rewritten around three criteria and now specify when a memory must be written rather than leaving it to judgement.
- Criteria are applicable, durable, legible
- Explicit MUST-save triggers: user corrections however phrased, skeptical questions, environment discoveries
- New rule that memory writes happen before the reply that engages the correction, not after the conversation settles
- The frontmatter template now includes a
metadata: pinned:field - Gated on
tengu_stone_shell, fallback false
A good memory is applicable, durable, and legible
Strings lifted out of the shipped bundle, so the claim above can be checked against them.