{"version":"2.1.224","anchor":"claude-plugin-eval-init-interactive-fails-clearly-without-a-","canonical_anchor":"claude-plugin-eval-init-interactive-fails-clearly-without-a-","heading":"claude plugin eval init --interactive fails clearly without a terminal","tier":"notice","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/claude-plugin-eval-init-interactive-fails-clearly-without-a-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### `claude plugin eval init --interactive` fails clearly without a terminal\n\nAsking for the eval interview without a terminal now fails clearly and tells you the alternative.\n\n**What**\n\nAsking for the interactive authoring interview when there is no real terminal attached now prints an explanation and exits 1, instead of trying to run the interview. The message tells you to either run it in a terminal or drop `--interactive` and pass a case name to get a blank template. There are two wordings depending on whether you supplied a case name.\n\n**Evidence**\n\n`The authoring interview requires an interactive terminal (TTY). Run `claude plugin eval init` in a terminal, or drop --interactive and pass a case name (e.g. `claude plugin eval init my-case`) to write a blank template instead.`\n\n**Usage**\n\n`claude plugin eval init my-case`\n\n- Area: Plugin Eval\n- Names: `--interactive`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}