{"version":"2.1.315","anchor":"ccr-catch-up-event-read-can-resume-from-an-anchor-event-id","canonical_anchor":"ccr-catch-up-event-read-can-resume-from-an-anchor-event-id","heading":"Remote sessions catch up on reconnect from where they left off","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/ccr-catch-up-event-read-can-resume-from-an-anchor-event-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Remote sessions catch up on reconnect from where they left off\n\nWhen a remote session reconnects, Claude Code can now fetch only the events after the last one it has, rather than up to 1,000\n\n**What**\n\nWhen a remote session reconnects, Claude Code fetches the events it missed so it can catch up. Before, it always asked for up to 1,000 events. It can now pass the ID of the last event it already has (`after_event_id`) and fetch only newer ones. If the server rejects that ID or cannot find it, Claude Code falls back the same way as before.\n\n**Why**\n\nLess data has to be sent when a remote session reconnects.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}