{"version":"2.1.299","anchor":"at-mention-files-can-be-served-from-a-pre-read-cache","canonical_anchor":"at-mention-files-can-be-served-from-a-pre-read-cache","heading":"@-mentioned files can arrive with their contents already attached","tier":"notice","area":"File Mentions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/at-mention-files-can-be-served-from-a-pre-read-cache","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### @-mentioned files can arrive with their contents already attached\n\nFiles you @-mention can now be sent with their contents if Claude Code already read them, while files that are too large are marked unread\n\n**Unclear.** It is not clear what reads files ahead of time, or whether that happens in ordinary sessions.\n\n**What**\n\nWhen you type `@` followed by a file name, Claude Code adds that file to your message. Before, every @-mention was passed on as a reference only, a pointer to the file without its contents.\n\nNow the outcome depends on the file:\n\n- Already read ahead of time and within a size and token limit: the contents are attached directly.\n\n- Not read ahead of time: the file stays a reference, as before.\n\n- Too large: the file is marked as unread, with the reason `too_large`.\n\n**Why**\n\nThis can change whether Claude sees a mentioned file's contents straight away or only a pointer to it.\n\n- Area: File Mentions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}