Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

Connector downloads and added folders are trusted less

Files from claude.ai connectors no longer load as skills, CLAUDE.md or MCP config, and added folders and connector file sends get stricter rules

Group of 3 You'll notice Improvements
JSON All of v2.1.319
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ConnectorsArea: what it touches
ImprovementsKind: in v2.1.319,
ImprovementsSection of the release

What

Claude Code saves files downloaded from claude.ai connectors (links to outside services) in a connector-downloads folder. Content there is no longer treated as configuration:

  • Skill folders, and folders added with --add-dir (extra working folders), are not loaded when they are in or beneath a connector-downloads folder. Claude Code logs a skip message and explains that the folder's skills and commands weren't loaded. Project skill folders also get extra handling for skills found in nested folders.
  • CLAUDE.md files inside such a folder are skipped, and a message is logged.
  • When Claude Code looks upward through parent folders for a project .mcp.json, it no longer reads one in a connector-downloads folder. A warning tells you to move or rename the folder. Adding or removing project-scope MCP servers there fails with "Cannot change .mcp.json here: this folder is in a connector-downloads folder".
  • Project-scope workflows can't be saved in or beneath a connector-downloads folder.

Added folders and sending files to connectors:

  • extraKnownMarketplaces and enabledPlugins in a folder added with --add-dir are ignored unless that folder is trusted. This applies when the server-controlled switch tengu_tawny_thrush is on, and nothing has been read about that switch. A warning explains how to fix it, and folders in Downloads are filtered out.
  • When Claude sends a file to a connector, paths through ..namedfork are refused. On macOS that is a hidden second part of a file, and the message says "this path goes through a file's named fork".
  • Long refusal messages explain how to use --add-dir or /add-dir.
  • Background-job sessions may only send files the user attached to the chat.
  • macOS screenshot names with AM/PM are retried with the other space character.
  • A host-mapped path option skips local path resolution.

Why

A file downloaded from a connector, or a folder you only meant to work in, can no longer quietly add skills, instructions, MCP servers or plugins to your session. When a file send is refused, the message tells you what to do.

See this entry in the whole of v2.1.319 →

Feedback