{"version":"2.1.235","anchor":"claude-plugin-eval-eval-dir-shipped-with-ownership-chec","canonical_anchor":"claude-plugin-eval-eval-dir-shipped-with-ownership-chec","heading":"claude plugin eval --eval-dir shipped, with ownership checks on where cases and results are written","tier":"use","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/claude-plugin-eval-eval-dir-shipped-with-ownership-chec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### `claude plugin eval --eval-dir` shipped, with ownership checks on where cases and results are written\n\nplugin eval's --eval-dir flag ships with checks that it isn't writing results to a symlinked or foreign-owned directory\n\nThe `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.\n\nThe 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.\n\n- Area: Plugin Eval\n- Names: `--eval-dir`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}