{"version":"2.1.300","anchor":"hook-fault-message-when-hook-lookup-breaks-inside-claude-cod","canonical_anchor":"hook-fault-message-when-hook-lookup-breaks-inside-claude-cod","heading":"Hook errors caused by Claude Code itself no longer send you to \/hooks","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/hook-fault-message-when-hook-lookup-breaks-inside-claude-cod","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Hook errors caused by Claude Code itself no longer send you to \/hooks\n\nWhen an internal fault stops Claude Code from finding the hooks for a call, the message now says nothing in the session can fix it\n\n**What**\n\nHooks are commands set up to run at set moments, such as before or after Claude uses a tool. Before an action, Claude Code works out which hooks apply to it. If that lookup fails because of a fault inside Claude Code, the action is blocked. The block message now says the fault is in Claude Code, that nothing in this session can fix it, and that a retry would be blocked the same way.\n\nBefore, the message always said to retry with a different input and to check your hooks in `\/hooks` or in your settings.\n\n**Why**\n\nThe old advice was misleading when the cause was an internal fault. Your hook setup was not the problem, so checking `\/hooks` would not help.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}