{"version":"2.1.251","anchor":"plugin-directories-on-network-paths-are-now-rejected","canonical_anchor":"plugin-directories-on-network-paths-are-now-rejected","heading":"Plugin directories on network paths are now rejected","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/plugin-directories-on-network-paths-are-now-rejected","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Plugin directories on network paths are now rejected\n\nPlugins installed from network shares or automounted paths are now refused.\n\n**What**\n\nWhen a plugin's location comes from running a shell command, Claude Code now refuses paths that are Windows UNC shares or automounted network locations, and refuses paths reached through a symlink that points to an untrusted network location. Both the resolved plugin directory and every entry inside it are checked.\n\n**Details**\n\n- Always applied when resolving a command-sourced plugin; there is no override.\n- The refusal says the path is a network path (UNC or automount) and is not supported as a plugin directory.\n\n**Evidence**\n\n`a network path (UNC or automount), which is not supported as a plugin directory`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}