Error / Message
A configured hook isn't running
A hook defined in settings.json isn't firing when expected — almost always a mismatch between the event name, matcher, or an executable permission issue.
The event name has to match exactly what Claude Code actually fires (like PreToolUse or Stop) — a small typo means the hook is technically configured but never triggered, since nothing matches it.
If the hook points at a script file, that file needs execute permission on the filesystem; a hook config that looks correct but references a non-executable script fails silently rather than with an obvious error.
A matcher that's too narrow (targeting a specific tool name that doesn't match how it's actually invoked) is the other common cause — broadening it temporarily is a fast way to confirm whether the matcher itself is the problem.
Check the hook's event name, matcher, and that any script file has execute permissionFrequently asked questions
What does "A configured hook isn't running" mean in Claude Code?
A hook defined in settings.json isn't firing when expected — almost always a mismatch between the event name, matcher, or an executable permission issue.
How do I fix it?
Try: Check the hook's event name, matcher, and that any script file has execute permission
Is this something to worry about?
A matcher that's too narrow (targeting a specific tool name that doesn't match how it's actually invoked) is the other common cause — broadening it temporarily is a fast way to confirm whether the matcher itself is the problem.
Is this covered in OG Flow Code Premium Toolkit?
Yes — A configured hook isn't running and patterns like it are covered by the commands, and in higher tiers the specialist agents and guided skills, in OG Flow Code Premium Toolkit. Tiers start at $19.90.
Want the full command, hook, and template pack?
This is one pattern from the OG Flow Code toolkit. Choose the tier that fits your workflow, including Multi-Stack for six additional language stacks.
See pricing — from $19.90 once