{"version":"2.1.247","anchor":"remote-memory-snapshots-move-from-a-transport-callback-to-a-","canonical_anchor":"remote-memory-snapshots-move-from-a-transport-callback-to-a-","heading":"Remote memory snapshots move from a transport callback to a conversation attachment","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/remote-memory-snapshots-move-from-a-transport-callback-to-a-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Remote memory snapshots move from a transport callback to a conversation attachment\n\nRemote memory snapshots now arrive as a conversation attachment rather than a transport callback.\n\n**What**\n\nMemory 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.\n\n**Details**\n\n- 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.\n- The attachment type is `cowork_memory_context`; a withdrawn snapshot carries null content.\n- Five new outcomes are logged: fetched, unchanged, none, malformed and gated.\n\n**Evidence**\n\n`The previous memory snapshot was withdrawn; disregard it.`\n\n- Flag `tengu_misty_anchor`: Not enough to say (read for one account on one subscription tier against v2.1.247; this account: no value returned, anonymous baseline: no value returned, compiled default: off)\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}