{"version":"2.1.287","anchor":"compaction-marker-rows-held-until-the-summary-arrives-in-ccr","canonical_anchor":"compaction-marker-rows-held-until-the-summary-arrives-in-ccr","heading":"Remote session transcripts upload a compaction marker together with its summary","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/compaction-marker-rows-held-until-the-summary-arrives-in-ccr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Remote session transcripts upload a compaction marker together with its summary\n\nIn remote sessions, the transcript row that marks a compaction is now held back and uploaded together with the summary\n\n**Unclear.** It is not clear whether this holding back always applies or only under some setting.\n\n**What**\n\nWhen a conversation gets too long, Claude Code compacts it: it replaces older messages with a summary, and leaves a marker in the transcript (the session's saved record) showing where that happened. In remote sessions the transcript is uploaded row by row.\n\nThe marker row used to be sent straight away. It is now held, along with any rows after it, until one of these happens, and then they are sent together:\n\n- the summary arrives\n\n- a user or assistant message arrives\n\n- too many rows have built up\n\n- a time limit runs out\n\n- the session closes\n\nWhen the time limit runs out first, Claude Code records that the marker went up without its summary.\n\n**Why**\n\nThe uploaded transcript of a remote session keeps the compaction marker next to its summary instead of leaving them apart.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}