Eval scaffolding refuses to create files outside a plugin or skill folder unless you pass --eval-dir.
What's wrong with this entry?
Running eval scaffolding outside a plugin or skill folder now errors and exits 1 instead of creating files where they do not belong, unless you pass --eval-dir. Output directories are also vetted: a symlinked base is refused, and when ownership vetting is on, so is a directory owned by another user.
- The refusal is recorded as
cwd_not_a_plugin. - Path checks throw an escape error rather than silently writing outside the intended base.
claude plugin eval init --eval-dir ./evals is not a plugin or skill folder
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.233
Plugin command help text comes from one table
Both mention eval init
-
v2.1.235
Eval runs record their output directory and show per-case advisories
Both mention eval init
-
v2.1.246
Project onboarding checklist gone
Both mention init