{"version":"2.1.318","anchor":"transcript-upload-holds-prompt-snapshot-attachment-rows-behi","canonical_anchor":"transcript-upload-holds-prompt-snapshot-attachment-rows-behi","heading":"Remote session transcripts change the order some entries are uploaded in","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/transcript-upload-holds-prompt-snapshot-attachment-rows-behi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Remote session transcripts change the order some entries are uploaded in\n\nRemote sessions may now hold back prompt snapshot entries until pending messages upload, changing transcript upload order\n\n**Unclear.** The holding rule comes from the server, so which sessions are affected is not known.\n\n**What**\n\nA remote session's transcript, the record of everything in the conversation, is uploaded line by line, and some lines wait for others to go first. Two things changed:\n\n- Prompt snapshot entries now wait only while a reply from Claude or a tool result in the main conversation is still being held back. Before, they followed the general waiting rules.\n\n- Virtual user entries, which are messages Claude Code adds itself rather than ones you typed, are now handled along with tool results instead of being skipped.\n\nWhether lines are held back at all depends on a rule the server sends.\n\n**Why**\n\nThis changes the order and timing in which a remote session's transcript appears, which matters if you read or process those transcripts elsewhere.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}