Unclear It is not clear what conditions make a plugin hook wait or fail the check, so whether a given plugin's hooks are affected is unsettled.
A hook is a command that Claude Code runs automatically at a set moment, such as before or after a tool is used. Plugins can bring their own hooks. Before this release, Claude Code matched a plugin's hooks by event alone. Now a plugin hook also has to pass an admission check before it is found and run.
When only managed hooks are allowed (hooks set by an organization's administrator), Claude Code can now hold a plugin's command source and wait. New error messages cover two cases:
- a plugin command source held while waiting for the organization's answer
- a plugin command source that was not started by a tool server daemon (a background process that runs tool servers)
In organizations that control which hooks may run, a plugin's hooks can now wait for the organization's decision instead of running straight away. If a plugin hook seems not to fire, one of these messages may explain why.
It is not clear what conditions make a plugin hook wait or fail the check, so whether a given plugin's hooks are affected is unsettled.