What
Install, uninstall, enable, disable, update and prune now raise a dedicated plugin-failure error when an operation reports failure. The shared handler only sends a report to error tracking when the error is neither that class nor otherwise classified, tagged per subcommand, so ordinary plugin failures stop being counted as unclassified crashes.
Evidence
plugin operation returned a failure result
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleclaude plugin
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Create and distribute a plugin marketplace touched a line naming claude plugin after this was published.
Test your marketplace before sharing. Validation checks file structure; to test whether a plugin changes what Claude does on realistic prompts, run its eval suite with [`claude plugin eval`](/docs/en/plugin-evals) before you publish a new …plugin-marketplaces see the edit
Confirmed since
Anthropic's documentation has since written up claude plugin, on Claude Code changelog.
* Added `--json` to `claude plugin install`, `uninstall`, `update`, `enable` and `disable`, and `errorDetails`/`noteDetails` to each row of `claude plugin list --json`changelog see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up claude plugin, on Claude Code changelog.