The same guard now applies to plugin hooks.json manifests: if PreToolUse or PermissionRequest appear outside the hooks key, or hooks isn't a proper object mapping event names to matcher arrays, loading now throws instead of proceeding with malformed config.
Names in the bundlehooks.json
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 Debug your configuration touched a line naming hooks.json after this was published.
| Hook never fires | Hooks are defined in a standalone file instead of `settings.json` | There is no standalone hooks file for project or user config. Define hooks under the `"hooks"` key in `settings.json`. Only [plugins](/docs/en/plugins…debug-your-config see the edit
Confirmed since
Anthropic's documentation has since written up hooks.json, on Plugins reference.
| `hooks` | string\|array\|object | Hook config paths or inline config | `"./my-extra-hooks.json"` |plugins-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 hooks.json, on Plugins reference.