{"version":"2.1.296","anchor":"bridge-transcript-catch-up-reworked-with-retries","canonical_anchor":"bridge-transcript-catch-up-reworked-with-retries","heading":"Remote sessions retry saving their history and refuse unsafe backfills","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/bridge-transcript-catch-up-reworked-with-retries","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Remote sessions retry saving their history and refuse unsafe backfills\n\nWhen a remote session catches up on saving its conversation history, Claude Code now retries and no longer starts saving after a failed catch-up\n\n**What**\n\nWhen a session is connected remotely, Claude Code keeps a saved record of the conversation, called the transcript. Catching that record up used to be a single attempt: if it failed, Claude Code logged the failure and started writing the transcript anyway. Now:\n\n- Catching up runs as a loop that retries, and ends as caught up, retried, late or fell behind.\n\n- If catching up fails, Claude Code does not start writing the transcript.\n\n- Filling in earlier history (backfill) is refused when the transcript contains an entry asking for history to be hidden.\n\n- Messages that were kept after compaction, which is when older conversation is summarised to save space, are protected during backfill.\n\n**Why**\n\nThe saved history of a remote session should be more reliable, and history that was meant to stay hidden is not written back in.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}