{"version":"2.1.305","anchor":"ccr-worker-processing-acks-ordered-behind-written-transcrip","canonical_anchor":"ccr-worker-processing-acks-ordered-behind-written-transcrip","heading":"Remote sessions send \"processing\" notices only after the transcript is written","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/ccr-worker-processing-acks-ordered-behind-written-transcrip","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Remote sessions send \"processing\" notices only after the transcript is written\n\nIn remote sessions, a \"processing\" notice for a held turn now waits until buffered transcript lines are written before it is sent\n\n**What**\n\nIn a remote session, Claude Code runs on another machine and reports back to the service. When it picks up a message, it sends an acknowledgement saying the message is being processed.\n\n- When a turn is held open across several calls to the model, the \"processing\" acknowledgement now waits until any buffered lines of the session transcript (the running record of the conversation) have been written.\n\n- Each acknowledgement is now tied to the ID of the message it answers.\n\n- Incoming events now also release uploads that were being held back.\n\nBefore, the acknowledgement was sent straight away without waiting for the transcript.\n\n**Why**\n\nThis changes the order in which acknowledgements and transcript lines arrive for remote sessions, so a message is not reported as being processed before the record of it exists.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}