{"version":"2.1.311","anchor":"transcript-writes-wait-for-remote-upload-or-shutdown","canonical_anchor":"transcript-writes-wait-for-remote-upload-or-shutdown","heading":"Saving the transcript remotely no longer holds up shutdown","tier":"notice","area":"Session Transcripts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/transcript-writes-wait-for-remote-upload-or-shutdown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Saving the transcript remotely no longer holds up shutdown\n\nRemote transcript uploads are now awaited only until upload finishes or Claude Code shuts down, and writes are kept in the order they were made\n\n**What**\n\nThe transcript is the saved record of a conversation. When Claude Code also saves it to a remote location, it now waits for each upload to finish or for shutdown to begin, whichever comes first. Before, it waited for the upload itself with no such release. Remote writes are also now carried out one after another, in the order they were requested.\n\n**Why**\n\nA slow upload can no longer keep Claude Code from closing. Keeping writes in order means the remote copy of the transcript builds up in the same sequence as the conversation.\n\n- Area: Session Transcripts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}