{"version":"2.1.296","anchor":"internal-event-reads-are-bounded-and-can-skip-encoded-bodies","canonical_anchor":"internal-event-reads-are-bounded-and-can-skip-encoded-bodies","heading":"Reading a session's internal event record can now be size-limited","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/internal-event-reads-are-bounded-and-can-skip-encoded-bodies","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Reading a session's internal event record can now be size-limited\n\nClaude Code can now limit how much of a session's internal event record it reads, and stops at oversized or encoded pages\n\n**What**\n\nClaude Code keeps a record of a session's internal events. When it reads this record back, it can now set limits on:\n\n- the number of events\n\n- the number of bytes\n\n- the length of each timestamp\n\nIf a limit is passed, or a page arrives compressed or otherwise encoded, Claude Code returns no events for it. Before, it read the record page by page with no limits.\n\n**Why**\n\nThis keeps a very large record from causing trouble when Claude Code resumes a subagent, a helper Claude starts to handle part of the work.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}