Plugin eval now tells you when it deliberately skipped loading a nearby plugin it doesn't trust.
What's wrong with this entry?
The early-access eval command resolves the target, the plugin root and any untrusted or adopted manifest directory before running, and prints a notice whenever a plugin it found is deliberately not loaded: one above the working directory, one outside the scope it consulted, or one whose ownership it cannot verify. Those cases run against baseline Claude instead of quietly loading someone else's plugin.
--eval-diris validated and vetted with its own refusal codeseval_dir_refusedandeval_dir_unvettable.- The eval directory may come from the plugin manifest.
- The "no results" help text now names the directory and manifest it actually consulted.
eval_dir_unvettable
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