Plugin eval runs now happen in a tighter sandbox with their own git repo and home directory.
What's wrong with this entry?
The bundled reference for claude plugin eval describes a redesigned sandbox: the working directory sits inside the sandbox home, an empty git repository at the sandbox home root stops git from walking up into your real repo, and the child process is started with --setting-sources user and the prompt passed on stdin instead of the command line. Enterprise managed settings are called out as the one policy that still applies inside a run.
- Adds exit code 143 for a run killed by SIGTERM, and an
auth_failedreason for a partial run. - Per-plugin failure codes appear under the suite's plugin list, and individual cases can carry advisories.
- Image and binary grading moved from "upcoming" to shipped.
- This is documentation text; the eval harness itself remains early-access gated.
--setting-sources user
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.235
plugin evalnow tells you when a nearby plugin is not being loadedBoth mention eval
-
v2.1.235
--eval-diron the eval command, with warnings that name the fixBoth mention eval
-
v2.1.235
Eval setup refuses directories it cannot vouch for
Both mention eval