You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
File AttachmentsArea: what it touches
ImprovementsKind: in v2.1.323,
ImprovementsSection of the release
Unclear It is not clear what a Drive entry 'not filled in here' is, or what skipping the declaration check when an answer arrives late changes for the user.
What
When Claude reads a file you mention, or attaches one, Claude Code first checks that the path is safe to use. These checks now say why a path was blocked, instead of only answering yes or no. A path blocked because its name looks like it holds credentials (passwords, keys or tokens) is now reported with that reason.
Attaching a file from a Drive entry that is not filled in here now has its own refusal reason. A Gmail entry already had one.
Why
It tightens how files are sent to connectors, the outside services Claude Code is linked to, and a refusal now says which rule stopped it.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what a Drive entry 'not filled in here' is, or what skipping the declaration check when an answer arrives late changes for…
