What
Typing @ and a path in a message attaches that file or folder for Claude to see. When a particular setting is on, Claude Code now checks these mentions more carefully before reading them.
- Path check: the path is resolved first to where it really points, then checked against permissions at that location.
- Fallback: if the location can't be settled or opening it is refused, the file is not read. It is passed as a reference marked
unread: "unexamined". - IDE files: the file attached because it is open in your editor gets the same check.
- Message to Claude: for an unexamined reference, Claude is told the mentions "could not be examined and were not attached". Other references keep the old wording, "File contents are not attached automatically in this session". Both still tell Claude to read the files itself.
Before, a mention was checked for permission and then read straight from the path, with no check of where the path really led.
Why
This closes a gap where a file could be swapped or redirected by a link between the permission check and the read. Some mentions may now appear as unread references, and Claude is given the correct reason.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear what makes Claude Code mark mentions as ones that could not be examined.