{"version":"2.1.274","anchor":"read-filebatch-file-read-now-take-bytebudget-and-admitpubli","canonical_anchor":"read-filebatch-file-read-now-take-bytebudget-and-admitpubli","heading":"read_file\/batch file read now take byteBudget and admitPublicRead options; new asset-existence HEAD check","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/read-filebatch-file-read-now-take-bytebudget-and-admitpubli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### read_file\/batch file read now take byteBudget and admitPublicRead options; new asset-existence HEAD check\n\nArtifact file-read functions gain options for public reads, byte limits, and a new file-existence check\n\n**What**\n\nThe functions that read a single artifact file or a batch of artifact files now accept extra options: whether to admit a public (non-member) read, and for batch reads, a byte budget limiting how much data is fetched at once. A new helper also does a quick existence check (an HTTP HEAD request, which asks whether a file exists without downloading it) for a specific artifact version's asset bundle.\n\n**Why**\n\nThese options let artifact file reads be tuned per request, controlling both who can read public artifacts and how much data a batch read pulls back, and let Claude Code confirm an asset exists before trying to fetch it.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}