{"version":"2.1.288","anchor":"ccr-client-upload-paths-and-break-count-headers","canonical_anchor":"ccr-client-upload-paths-and-break-count-headers","heading":"Changes to how remote sessions upload their events","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/ccr-client-upload-paths-and-break-count-headers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Changes to how remote sessions upload their events\n\nRemote sessions can now upload events by other routes, send events together, and hold some reports until the sender is attached\n\n**Unclear.** It is not clear what turns on the other upload routes or who receives them.\n\n**What**\n\nIn a remote session, one that runs on another machine, Claude Code uploads a stream of events so the session can be followed and replayed. Several parts of this have changed:\n\n- Events can go through other upload routes when these are provided, instead of always the same uploader.\n\n- Events can be written together as one group.\n\n- Requests can carry headers marking an upload fallback and counting breaks.\n\n- Reports that nobody is listening are held back while the sender may not be connected yet.\n\n- When nobody is listening, events are sent less often.\n\n**Why**\n\nThis changes how remote-session events are uploaded and replayed.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}