What
When a plugin's hooks module (the file defining its custom hooks) is skipped — because of the CLAUDE_CODE_ENABLE_FUNCTION_HOOKS gate, disableAllHooks, --bare mode, or allowManagedHooksOnly — Claude Code already logged the reason to a debug log. Now it also delivers that reason directly to the owning plugin, through a new notification path, deduplicated so the same message isn't repeated.
Why
This makes it easier for a plugin author to find out why their hooks aren't loading without having to dig through debug logs.
Names in the bundleCLAUDE_CODE_ENABLE_FUNCTION_HOOKS--bare
Documented inclaude-code/plugins/mods/admin
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 --bare, on Environment variables.
| `CLAUDE_CODE_SIMPLE` | Set to `1` to run with a minimal system prompt and only the Bash, file read, and file edit tools. MCP tools from `--mcp-config` are still available. Disables auto-discovery of hooks, skills, custom commands, subage…env-vars see the edit
Added since
A small documentation edit on CLI reference touched a line naming --bare after this was published.
| `--bare` | Minimal mode: skip auto-discovery of hooks, skills, custom commands, subagents, installed plugins, MCP servers, auto memory, and CLAUDE.md so scripted calls start faster. Skills in a directory you pass with `--add-dir` still l…cli-reference see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on CLI reference touched a line naming --bare after this was published.