{"version":"2.1.312","anchor":"remote-upload-flush-no-longer-waits-on-start-row-timers","canonical_anchor":"remote-upload-flush-no-longer-waits-on-start-row-timers","heading":"Remote sessions drop one of the waits before uploading events","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/remote-upload-flush-no-longer-waits-on-start-row-timers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Remote sessions drop one of the waits before uploading events\n\nRemote sessions no longer hold uploads back behind start rows, leaving only the waits for settings answers and start-up\n\n**What**\n\nIn a remote session, meaning one where Claude Code runs on a remote machine rather than on your computer, Claude Code uploads a stream of events describing what happens. Before sending them, it can hold some events back briefly so they arrive in a sensible order. One of these holds, which waited behind the rows that mark the start of something, has been removed. The waits for settings answers and for start-up remain.\n\nA hold that kept some requesting rows back is also now skipped in some cases where the reply has already been streamed.\n\n**Why**\n\nThis changes how remote sessions batch the events they upload. How long the remaining waits last is decided by the server, so how much difference this makes in practice can vary.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}