Plugin manifests, marketplace entries, and agent frontmatter that declare PreToolUse/PermissionRequest hooks at the top level, under an unrecognized key, or nested in arrays this build cannot parse, now cause the plugin or agent to be rejected as "unloadable" with an explicit message, instead of failing validation silently elsewhere.
Names in the bundlePreToolUsePermissionRequest
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 Choose a permission mode touched a line naming PreToolUse after this was published.
If you set `dontAsk` mode, Claude Code auto-denies every tool call that would otherwise prompt you. Claude still runs actions that need no approval in Manual mode, such as file reads inside your working directories and [read-only Bash comm…permission-modes see the edit
Confirmed since
Anthropic's documentation has since written up PermissionRequest, on Claude Code changelog.
* Fixed PermissionRequest hooks not firing in `--print` modechangelog see the edit
Confirmed since
Anthropic's documentation has since written up PreToolUse, on migration.
| `PreToolUse` / `PostToolUse` hooks | Your client already sees every `agent.custom_tool_use` event before responding; put the logic there. For built-in tools, use `permission_policy: always_ask` to review every call. [`auto`](https://plat…managed-agents/migration 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 PreToolUse, on migration.