The Update Config skill helps Claude change your Claude Code settings, including hooks (commands that run automatically on certain events). After adding a hook, it used to always tell you to open /hooks once to reload the settings, or restart.
Where the /hooks menu is not available, it now tells you to start a new session so the new settings load, or to review the hook in the settings file that was written. Everywhere else it still points to /hooks.
This stops Claude from telling people, for example those using Claude Code through the SDK or remotely, to open a menu they do not have.
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.
* **As a deterministic gate**: a [Stop hook](/docs/en/hooks#stop) runs your check as a script and blocks the turn from ending until it passes. [Stop input](/docs/en/hooks#stop-input) covers the cap on consecutive blocks.best-practices see the edit
| Hooks | `hooks/hooks.json` | Hook configuration |plugins/manifest-reference see the edit
It is not clear exactly which environments count as having no `/hooks` menu.
Anthropic's documentation has since written up /hooks, on Plugin manifest reference.