{"version":"2.1.310","anchor":"session-ingress-batch-limit-and-event-reading-tweaks","canonical_anchor":"session-ingress-batch-limit-and-event-reading-tweaks","heading":"Size limit on uploaded batches of session events now comes from a different value","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/session-ingress-batch-limit-and-event-reading-tweaks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Size limit on uploaded batches of session events now comes from a different value\n\nThe maximum size of a batch of session events Claude Code sends to the server is now set by a different fixed value\n\n**What**\n\nClaude Code sends events from a session to the server in batches. The largest size such a batch may have is now taken from a different fixed value than before. Claude Code also now keeps track of an extra piece of information while it reads those events.\n\n**Why**\n\nThis may change how large each upload is and how events are grouped into batches.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}