The eval command reads its directory from a flag or the manifest, warning clearly when the value is malformed.
What's wrong with this entry?
The early-access plugin eval command takes --eval-dir <dir>, or reads the directory from the plugin manifest, with evals/ as the fallback; a mis-shaped manifest value produces a warning that says what to change.
- Case discovery checks the target path for trust before walking it, and resolves relative paths against the working directory.
- The error shown when an ablation run has no plugin now suggests targeting the plugin directory itself.
--eval-dir <dir>
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