{"version":"2.1.275","anchor":"turn-handoff-can-now-carry-a-memory-context-line","canonical_anchor":"turn-handoff-can-now-carry-a-memory-context-line","heading":"Turn handoffs can now carry a memory_context, including a laptop-specific tag","tier":"soon","area":"Turn Handoff","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/turn-handoff-can-now-carry-a-memory-context-line","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Turn handoffs can now carry a memory_context, including a laptop-specific tag\n\nHandoffs between sessions can carry a memory_context, tagged for laptop sessions, and tracked in bug-report telemetry\n\n**What**\n\nWhen work is handed off between sessions (for example between a laptop and another environment, a feature sometimes called \"cowork\"), the handoff can now carry extra memory information:\n\n- Handoff payloads can include an optional `memory_context` field alongside the existing `relay_marker` field.\n\n- If it's valid and not already used, it's attached to the handoff as a `cowork_memory_context` entry (with a version and content). If it's malformed or conflicts with something already present, it's logged and the handoff continues without it.\n\n- When the memory context is built for a laptop session specifically, it's tagged with `leg: \"laptop\"`.\n\n- When you submit a bug report or feedback, the report's telemetry now includes a `laptop_memory_rows_dropped` count, tracking how many of these laptop-tagged memory context entries were stripped out of the transcript before the report was sent.\n\n**Why**\n\nThis lets Claude Code carry richer memory context across a handoff between devices while keeping track of, and excluding, laptop-specific memory data from bug reports so it isn't sent along unnecessarily.\n\n- Area: Turn Handoff\n- Names: `memory_context`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 2\/5"}