{"version":"2.1.287","anchor":"session-event-upload-holds-back-rows-until-a-compact-summary","canonical_anchor":"session-event-upload-holds-back-rows-until-a-compact-summary","heading":"Remote sessions hold back some transcript entries until a compaction summary is ready","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/session-event-upload-holds-back-rows-until-a-compact-summary","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Remote sessions hold back some transcript entries until a compaction summary is ready\n\nIn remote sessions, some transcript entries now wait for a compaction summary before upload, and those still waiting at close are dropped or counted\n\n**Unclear.** Which entries get held back is not known.\n\n**What**\n\nIn a remote session, Claude Code uploads the session's events, its running record, as it goes. Compaction is when Claude Code shrinks a long conversation by replacing older parts with a summary. Some entries are now held back until that summary arrives.\n\nWhile entries are held back:\n\n- They count toward the number of events still waiting to be uploaded.\n\n- No more internal events are accepted for upload.\n\n- If the session closes first, they are dropped or counted, and the close also stops work still in progress.\n\n**Why**\n\nThis changes the order in which a remote session's transcript is uploaded around compaction.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}