{"version":"2.1.307","anchor":"worker-event-uploads-can-ride-on-the-same-post-sync-status","canonical_anchor":"worker-event-uploads-can-ride-on-the-same-post-sync-status","heading":"Hosted sessions can send event data in fewer requests","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/worker-event-uploads-can-ride-on-the-same-post-sync-status","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Hosted sessions can send event data in fewer requests\n\nSessions hosted by Anthropic can now send transcript rows and events together in one request, falling back to separate requests when refused\n\n**What**\n\nWhen Claude Code runs as a session hosted by Anthropic, it reports events and transcript rows to the service. It can now attach transcript rows to the same request it uses for events, instead of sending them separately. If the service refuses this, Claude Code goes back to sending them separately and records that it did.\n\nOther related changes:\n\n- Internal events are now offered to the same events request first.\n\n- Updates to a session's status details can wait for a particular status before they are sent.\n\n- The size of each batch of data now adjusts, up to the largest batch the connection allows.\n\n**Why**\n\nHosted sessions make fewer separate network requests.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}