{"version":"2.1.242","anchor":"claude-plugin-eval-init-refuses-to-scaffold-in-the-wrong-dir","canonical_anchor":"claude-plugin-eval-init-refuses-to-scaffold-in-the-wrong-dir","heading":"claude plugin eval init refuses to scaffold in the wrong directory","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/claude-plugin-eval-init-refuses-to-scaffold-in-the-wrong-dir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### `claude plugin eval init` refuses to scaffold in the wrong directory\n\nEval scaffolding refuses to create files outside a plugin or skill folder unless you pass --eval-dir.\n\n**What**\n\nRunning 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.\n\n**Details**\n\n- The refusal is recorded as `cwd_not_a_plugin`.\n- Path checks throw an escape error rather than silently writing outside the intended base.\n\n**Usage**\n\n`claude plugin eval init --eval-dir .\/evals` **Evidence** ` is not a plugin or skill folder`\n\n- Area: Plugins\n- Names: `claude plugin eval init`, `--eval-dir`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}