{"version":"2.1.323","anchor":"file-mention-reads-pending-credential-name-check-and-drive","canonical_anchor":"file-mention-reads-pending-credential-name-check-and-drive","heading":"Clearer reasons when Claude Code refuses to attach a file","tier":"notice","area":"File Attachments","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/file-mention-reads-pending-credential-name-check-and-drive","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Clearer reasons when Claude Code refuses to attach a file\n\nClaude Code now has its own refusal reason for a Drive entry not filled in here, and reports credential-like file names as the reason for a block\n\n**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.\n\n**What**\n\nWhen 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.\n\nAttaching a file from a Drive entry that is not filled in here now has its own refusal reason. A Gmail entry already had one.\n\n**Why**\n\nIt tightens how files are sent to connectors, the outside services Claude Code is linked to, and a refusal now says which rule stopped it.\n\n- Area: File Attachments\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}