{"version":"2.1.242","anchor":"plugin-symlinks-that-escape-the-plugin-directory-are-refused","canonical_anchor":"plugin-symlinks-that-escape-the-plugin-directory-are-refused","heading":"Plugin symlinks that escape the plugin directory are refused with a reason","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/plugin-symlinks-that-escape-the-plugin-directory-are-refused","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Plugin symlinks that escape the plugin directory are refused with a reason\n\nPlugin symlinks pointing outside the plugin directory are refused, each case with its own message.\n\n**What**\n\nWhen loading a plugin or skill, Claude Code now checks each part of a symlink's target and refuses links that leave the plugin's own directory tree, route above it, point back at the plugin directory itself, or land in repository metadata. Each case gets its own message.\n\n**Details**\n\n- Eval case discovery separately refuses `mocks\/` as a case directory name.\n\n**Evidence**\n\n`is a symlink that leaves the plugin tree`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}