The if_version requirement on memory writes sits behind a gate that defaults to false.
A build-gated change to the memory tools makes every write carry if_version: either the 12-character version token returned by the most recent read or write of that path, or the literal word new for a document that does not exist yet. The model therefore has to read a document before overwriting it. Reads now return the token; listing does not. Off in this build unless the tengu_haze_glass gate is on, which defaults to false.
- A stale token, or
newagainst a path that already exists, rejects the write and returns the current content (when it fits within the read size cap) plus its current version, so the model can merge and retry. - Rejections are recorded as
tengu_memory_tools_version_conflictwith the reason.
Every ${lS} needs if_version. Pass the literal word new for a document that does not yet exist.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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: 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
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.
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.