A withheld-memory-context live event is handled end to end but the store behind it needs tengu_misty_anchor.
The cloud connection gained a new live event type that tells Claude Code whether the server is withholding your memory context. The handling is wired end to end: a withheld notice drops the cached context, anything else triggers a re-fetch. The store it feeds is behind the same tengu_misty_anchor and entrypoint switch as the rest of memory context, so on a build without that turned on, nothing is fetched even when the event arrives.
- The transport gained a field and a
setOnMemoryContextStatussetter next to its existing heartbeat probe, and the event dispatcher routes the new frame to it carrying whether the payload marked the context withheld. - With the gate off, the receiving handler returns early after clearing the cache.
memory_context_status
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_misty_anchor Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.246: off
Read once, for one account on one subscription tier, against v2.1.246. 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.
New in this build: tengu_misty_anchor