{"version":"2.1.317","anchor":"plugin-folders-and-entries-now-checked-against-containment","canonical_anchor":"plugin-folders-and-entries-now-checked-against-containment","heading":"Plugin folders that point outside the plugin are no longer loaded","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/plugin-folders-and-entries-now-checked-against-containment","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Plugin folders that point outside the plugin are no longer loaded\n\nClaude Code now skips plugin folders and entries that reach outside their allowed location, reporting a path-traversal error\n\n**What**\n\nWhen a plugin loads, Claude Code now checks that each of its folders stays inside the location the plugin is allowed to use. It used to take these folders as given. The check covers these folders:\n\n- commands\n\n- agents\n\n- skills\n\n- output-styles\n\n- themes\n\n- workflows\n\nIndividual skill, theme and workflow entries inside those folders are checked as well. A plugin that belongs to a project must stay inside that project's folder. Anything that reaches outside is skipped, with an error of type `path-traversal` and a log line saying the folder was not loaded.\n\n**Why**\n\nA plugin can no longer use a link or an unusual path to make Claude Code read files from elsewhere on your computer. If a plugin you rely on stops loading a folder, it is likely pointing outside its own location.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}