{"version":"2.1.251","anchor":"oversized-files-rejected-without-reading-them-fully","canonical_anchor":"oversized-files-rejected-without-reading-them-fully","heading":"Oversized files rejected without reading them fully","tier":"notice","area":"Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/oversized-files-rejected-without-reading-them-fully","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Oversized files rejected without reading them fully\n\nReading an oversized file fails fast instead of eating memory.\n\n**What**\n\nThe Read tool no longer loads an entire file before deciding it is too big. Both the sync and async paths now read at most one byte past the limit and fail on the bytes actually read, so reading a huge file no longer costs the memory of the whole file.\n\n**Details**\n\n- Failure is still reported as a file-too-large error.\n- The size check now lives in a single shared helper used by both paths.\n\n**Evidence**\n\n`File exceeds maxBytes limit`\n\n- Area: Tools\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}