{"version":"2.1.290","anchor":"at-mentioned-files-now-read-through-a-hook-aware-path","canonical_anchor":"at-mentioned-files-now-read-through-a-hook-aware-path","heading":"Files you @-mention are read in a way hooks can take part in","tier":"notice","area":"File Attachments","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/at-mentioned-files-now-read-through-a-hook-aware-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Files you @-mention are read in a way hooks can take part in\n\n@-mentioned files are now read through a new path that can carry hook context, roll back on failure and filter folder listings\n\n**Unclear.** What the new read step does in detail, and whether it is switched on for everyone, is not clear.\n\n**What**\n\nWhen you type `@` followed by a file name to attach it to your message, Claude Code now reads the file through a new route:\n\n- the result can carry context from hooks, which are commands you configure to run at set points\n\n- a read started by a hook can be refused with \"the path may not be read here\"\n\n- if a read fails, Claude Code restores its earlier record of which files it had read\n\n- an @-mentioned folder is filtered, rather than listing its first 1000 entries and a count of the rest\n\n**Why**\n\nHooks can now be involved when you @-mention a file, and a failed read no longer leaves a wrong record behind, so what Claude sees from a mention can differ.\n\n- Area: File Attachments\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}