{"version":"2.1.235","anchor":"plugin-eval-warns-when-the-eval-directory-overlaps-the-plugi","canonical_anchor":"plugin-eval-warns-when-the-eval-directory-overlaps-the-plugi","heading":"plugin eval warns when the eval directory overlaps the plugin's declared component paths","tier":"notice","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/plugin-eval-warns-when-the-eval-directory-overlaps-the-plugi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### plugin eval warns when the eval directory overlaps the plugin's declared component paths\n\nplugin eval warns or errors when its eval directory overlaps a plugin's own command, agent, or MCP server paths\n\nBefore running, `plugin eval` now reads the plugin manifest's declared component paths \u2014 commands, agents, skills, outputStyles, themes, workflows, monitors, mcpServers, lspServers, and hooks \u2014 follows symlinks into the real tree, and checks whether the eval directory overlaps any of them, since files written there could otherwise be loaded as plugin components.\n\nWhen the directory came from `--eval-dir`, an overlap is a hard error unless the run doesn't write into the plugin. When it came from the manifest or the default location, it's downgraded to a warning that suggests `--output-dir` or running from the plugin root instead.\n\n- Area: Plugin Eval\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}