{"version":"2.1.239","anchor":"plugin-path-errors-name-broken-links-and-junctions","canonical_anchor":"plugin-path-errors-name-broken-links-and-junctions","heading":"Plugin path errors name broken links and junctions","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/plugin-path-errors-name-broken-links-and-junctions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Plugin path errors name broken links and junctions\n\nPlugin path errors now name broken links or junctions as a likely cause.\n\n**What**\n\nWhen a plugin path supplied by a repository passes through a component Claude Code cannot inspect, the refusal now names \"a link or junction whose target does not exist\" as a possible cause.\n\n**Details**\n\n- The accompanying hint escapes the plugin name before printing it.\n- The directory walk behind the check now separates a symlink pointing at a real directory from a redirect encountered on the first path component.\n\n**Evidence**\n\n`a link or junction whose target does not exist`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}