{"version":"2.1.319","anchor":"ccr-worker-init-can-resume-from-a-transcript-position-shutd","canonical_anchor":"ccr-worker-init-can-resume-from-a-transcript-position-shutd","heading":"Cloud sessions can pick up from a saved point in the transcript when reconnecting","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/ccr-worker-init-can-resume-from-a-transcript-position-shutd","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Cloud sessions can pick up from a saved point in the transcript when reconnecting\n\nCloud session workers can now resume from a point in the transcript, retrying without it if refused, and shutdown waits for a bounded time\n\n**What**\n\nIn a cloud session, the conversation runs on a remote machine called a worker. When a worker starts, Claude Code can now tell the server which point in the transcript to continue from. The transcript is the saved record of the conversation. If the server refuses that position, Claude Code asks again without it.\n\nWhen the worker shuts down, the final sending of pending events is now limited by how much time is left, so shutdown does not wait past its budget.\n\n**Why**\n\nThis is meant to make reconnecting to a remote session more reliable.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}