{"version":"2.1.299","anchor":"remote-worker-ccr-client-socket-transport-bigger-batch-b","canonical_anchor":"remote-worker-ccr-client-socket-transport-bigger-batch-b","heading":"Remote sessions gain a new connection for requests and retry with smaller batches","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/remote-worker-ccr-client-socket-transport-bigger-batch-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Remote sessions gain a new connection for requests and retry with smaller batches\n\nThe client that runs remote sessions can now use a new connection, retry failed sends in smaller pieces and drop orphaned records\n\n**What**\n\nWhen Claude Code runs as a worker for a remote session, one that runs somewhere other than your own machine, its connection code has changed:\n\n- A new connection can carry requests and heartbeats, the regular signals that show the worker is still alive.\n\n- If sending fails, it can retry with a smaller batch.\n\n- The default size limit for a batch of internal events is no longer the fixed 10,485,760 bytes. The new connection can set its own limit.\n\n- Handed-off records that no longer belong to anything are dropped and logged.\n\n**Why**\n\nThese changes concern the reliability of remote sessions.\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"}