{"version":"2.1.235","anchor":"plugin-eval-can-target-a-non-default-eval-directory","canonical_anchor":"plugin-eval-can-target-a-non-default-eval-directory","heading":"plugin eval can target a non-default eval directory","tier":"use","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/plugin-eval-can-target-a-non-default-eval-directory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### `plugin eval` can target a non-default eval directory\n\n`claude plugin eval` gets an `--eval-dir ` flag to target a non-default eval directory\n\nThe `plugin eval` command accepts a new `--eval-dir <dir>` flag, and the eval directory can also come from a plugin manifest's `experimental.evals` key; `evals\/` remains the fallback, and mis-shaped manifest values produce warnings that name the fix. Case discovery now screens the target path for trust before walking it and resolves it relative to the working directory. The error text shown when ablation runs with no plugin was rewritten to suggest targeting the plugin directory itself.\n\n- Area: Plugin Eval\n- Names: `--eval-dir`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}