Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MemoryArea: what it touches
In DevelopmentKind: in v2.1.247,
In DevelopmentSection of the release
What
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.
Details
Requires CLAUDE_CODE_ENTRYPOINT to be one of remote_cowork, remote_cowork_trigger, remote_api or remote_trigger, and the gate tengu_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.
Evidence
The previous memory snapshot was withdrawn; disregard it.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Read from
Feature flag
tengu_misty_anchorNot enough to say
Nothing 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: off
Flag reading movedThe flag server now returns off for tengu_misty_anchor, read as this 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.
Flag reading movedThe flag server now returns nothing at all, having stopped carrying it for tengu_misty_anchor, read as this 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.
