Remote memory snapshots now arrive as a conversation attachment rather than a transport callback.
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.247: on
Read once, for one account on one subscription tier, against v2.1.247. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Memory context for remote cowork sessions is no longer delivered through a handler on the streaming transport. It is fetched separately and inserted into the conversation as an attachment shown as a meta user message. When the server withdraws a snapshot, the attachment arrives empty and the model is told to disregard it. Nothing here is reachable in a normal local session.
- Requires
CLAUDE_CODE_ENTRYPOINTto be one ofremote_cowork,remote_cowork_trigger,remote_apiorremote_trigger, and the gatetengu_misty_anchor, whose compiled fallback is false. With no server saying otherwise, it stays off. - The attachment type is
cowork_memory_context; a withdrawn snapshot carries null content. - Five new outcomes are logged: fetched, unchanged, none, malformed and gated.
The previous memory snapshot was withdrawn; disregard it.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.