{"version":"2.1.319","anchor":"connector-file-sends-need-a-human-allow-at-the-terminal-prom","canonical_anchor":"connector-file-sends-need-a-human-allow-at-the-terminal-prom","heading":"Sending files to a connector now needs you to click Allow in the terminal","tier":"notice","area":"Connectors","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/connector-file-sends-need-a-human-allow-at-the-terminal-prom","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Sending files to a connector now needs you to click Allow in the terminal\n\nClaude Code now refuses to send files to a connector unless a person approves the request at Claude Code's own terminal prompt\n\n**Unclear.** It is not stated which tools count as sending files to a connector.\n\n**What**\n\nA connector is an outside service, such as one linked from claude.ai, that Claude can use through tools. Claude Code now sends files to a connector only after you answer Claude Code's own permission prompt in a terminal.\n\nThe send is refused when it runs:\n\n- in a background job\n\n- in a nested session, which is a Claude Code session started inside another one\n\n- in a teammate pane\n\nIt is also refused when the approval came from somewhere other than you at that prompt:\n\n- a hook, which is a script you set up to run at certain points\n\n- a plugin\n\n- a permission mode that approves calls automatically\n\n- an outside surface, such as another app\n\nWhen a send is refused, Claude Code gives a reason, for example that you were not asked, that the request changed after it was approved, or that there is no prompt available where it ran.\n\n**Why**\n\nFiles cannot leave your machine for a connector without a person agreeing. Text that tricks the model, or a setting that approves everything, cannot get around that.\n\n- Area: Connectors\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}