{"version":"2.1.319","anchor":"connector-downloaded-files-are-fenced-off-from-reads-settin","canonical_anchor":"connector-downloaded-files-are-fenced-off-from-reads-settin","heading":"Files downloaded from claude.ai connectors are kept out of reads, settings and cloud sessions","tier":"notice","area":"Connectors","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/connector-downloaded-files-are-fenced-off-from-reads-settin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Files downloaded from claude.ai connectors are kept out of reads, settings and cloud sessions\n\nClaude Code now refuses to read connector-downloaded files in some cases, ignores settings files in connector-downloads folders, and blocks cloud sessions from them\n\n**What**\n\nConnectors on claude.ai link Claude to outside services and can download files. Claude Code now treats those files, and anything in a connector-downloads folder, more carefully:\n\n- The Read tool, which Claude uses to open files, refuses them when your organization keeps connector data out of conversations that can reach the web.\n\n- The Read tool also refuses them when sending to a session on another machine.\n\n- Settings files inside a connector-downloads folder are not used, and a notice on stderr says so.\n\n- Starting a cloud session from a connector-downloads folder fails, with advice to start from a folder outside it.\n\n- Other reads of downloaded files get a note attached.\n\n**Why**\n\nThis sets a new security boundary around files that came from connectors, so their contents do not leak into places your organization has kept them out of, and so a downloaded file cannot change how Claude Code is configured.\n\n- Area: Connectors\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}