{"version":"2.1.318","anchor":"at-mentioned-oversized-files-become-a-reference-instead-of-be","canonical_anchor":"at-mentioned-oversized-files-become-a-reference-instead-of-be","heading":"Oversized @-mentioned files are now announced to Claude with instructions to read them fully","tier":"notice","area":"File Mentions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/at-mentioned-oversized-files-become-a-reference-instead-of-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Oversized @-mentioned files are now announced to Claude with instructions to read them fully\n\nA file mentioned with @ that is too large to attach now becomes a reference, and Claude is told to read all of it in portions\n\n**What**\n\nYou can point Claude at a file by typing @ followed by its name. When that file is too large to include in the message, Claude Code now handles it differently.\n\n- Before, the mention was silently dropped. Now it becomes an `at_mention_reference` marked unread for being `too_large`, and it includes the file's size (`fileSize`).\n\n- The file is also tagged `readAllOfIt: 'over_size_limit'`. A file that fails the size check in tokens and is also over the byte limit is now listed as unread rather than skipped. Tokens are the small chunks of text the model counts.\n\n- The note sent to Claude says: \"It was too large to attach, so you have not seen any of it.\"\n\n- Claude is told to read the whole file in portions using `offset` and `limit`, unless your request needs only part of it. The note says how many reads that will take, at roughly 60 KB or 25,000 tokens per read.\n\n- Before, the note told Claude to read in portions, or to read the whole file in one call if it truly needed all of it.\n\n- Claude is also told to tell you when its answer comes from searches or a partial read.\n\n- A new notice tells Claude that project docs and PDFs were read before its reply, for example \"The PDF file that came with this message was read before your reply\".\n\n**Why**\n\nClaude now knows a large mentioned file exists instead of never hearing about it. You should see answers based on the whole file more often, and be told when an answer comes from only part of it.\n\n- Area: File Mentions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}