plugin eval's --eval-dir flag ships with checks that it isn't writing results to a symlinked or foreign-owned directory
The claude plugin eval init path now accepts an eval directory either from the --eval-dir flag or from the plugin manifest's experimental.evals key. It refuses to consult a manifest sitting in a directory it cannot vouch for, refuses to write cases or results into a symlinked or foreign-owned location, and cleans up any directory it created if the run fails partway through.
The bundled plugin-eval reference docs were updated to match: earlier notes calling --eval-dir an upcoming feature are gone, and the flag is now listed among the documented options.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
| `experimental.evals` | string\|array | Directory below the plugin root that holds the plugin's [eval cases](/docs/en/plugin-evals#use-a-different-eval-directory), when it isn't the default `evals/`. `claude plugin eval --eval-dir` overri…plugins-reference see the edit
Anthropic's documentation has since written up --eval-dir, on Plugins reference.
New in this build: --eval-dir