Eval warns when your eval directory overlaps paths the plugin already loads components from.
What's wrong with this entry?
Before running, the eval command reads the component paths declared in plugin.json (commands, agents, skills, outputStyles, themes, workflows, monitors, mcpServers, lspServers, hooks), follows symlinks into the real tree, and reports when the eval directory sits inside one, because files written there could be loaded as plugin components.
- With
--eval-dirthis is a hard error, unless the run writes nothing into the plugin. - When the directory came from the manifest or the default, it is a warning that suggests
--output-diror running from the plugin root.
files written there may be loaded as plugin components
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
plugin evalno longer swallows piped inputBoth mention eval
-
v2.1.234
Plugin eval reference documents image grading and new exit codes
Both mention eval
-
v2.1.234
claude plugin evalhandles termination signals and cleans up its outputBoth mention eval