What
The CLI's claude plugin test --file and claude plugin test commands now use a single shared helper, pluginTestRefusal, to decide why a plugin's hook-module tests can't run, replacing scattered inline conditional logic. The helper reports one of two reasons:
- If the hooks-modules feature isn't enabled yet, it tells the user to set
CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1. - If the feature is enabled but hook modules are disabled locally (for example via
disableAllHooks,allowManagedHooksOnly, or an organization policy), it reports that instead.
Why
This gives a consistent, accurate explanation when plugin test refuses to run, instead of an unclear or inconsistent message, making it easier to figure out whether the fix is an environment variable or a local/managed policy setting.
Names in the bundleclaude plugin test
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.
Confirmed since
Anthropic's documentation has since written up claude plugin test, on Plugin commands reference.
claude plugin test [directory]plugins/cli-reference 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 test, on Plugin commands reference.