{"version":"2.1.224","anchor":"plugin-eval-report-publishing-flags-reworked","canonical_anchor":"plugin-eval-report-publishing-flags-reworked","heading":"plugin eval: report publishing flags reworked","tier":"use","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/plugin-eval-report-publishing-flags-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### plugin eval: report publishing flags reworked\n\nPlugin eval publishes its HTML report by default; --publish-report now means require publishing.\n\n**What**\n\n`claude plugin eval` now publishes the HTML report by default when your account supports it. `--publish-report` changed meaning to \"require publishing\", and explains why if it is unavailable; `--no-publish` keeps the report local. Passing both is now an error. `--report` now means the report replaces the results directory, implying a default location.\n\n**Details**\n\n- Results from the LLM judge on long inputs now append an advisory suggesting a regex grader instead.\n\n**Evidence**\n\n`Error: --no-publish and --publish-report are contradictory \u2014 pass at most one.`\n\n- Area: Plugin Eval\n- Names: `--publish-report`, `--no-publish`, `--report`, `claude plugin eval`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}