Eval setup refuses directories with unverifiable ownership or symlinks, and cleans up after a failed setup.
What's wrong with this entry?
When setting up evals, the command takes the directory from --eval-dir or the plugin manifest's experimental.evals, refuses to read a manifest in a directory whose ownership it cannot confirm, refuses symlinked or foreign-owned output locations, and removes any directories it created if setup fails.
- The bundled plugin-eval reference documents were updated to match: the notes calling
--eval-diran upcoming release are gone and the flag is listed among the options. - The eval command itself remains early-access gated.
pass --eval-dir to name the directory
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