Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.275 ·

Turn handoffs can now carry a memory_context, including a laptop-specific tag

Handoffs between sessions can carry a memory_context, tagged for laptop sessions, and tracked in bug-report telemetry

TierNothing to try yethow much it should matter to you
Useful3my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaTurn Handoffwhat it touches
KindImprovementsin v2.1.275,
Group of 4 Nothing to try yet No documentation found

Handoffs between sessions can carry a memory_context, tagged for laptop sessions, and tracked in bug-report telemetry

What

When 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:

  • Handoff payloads can include an optional memory_context field alongside the existing relay_marker field.
  • 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.
  • When the memory context is built for a laptop session specifically, it's tagged with leg: "laptop".
  • 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.

Why

This 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.

Read from
Names in the bundlememory_context

See this entry in the whole of v2.1.275 →

Feedback