Claude Code hooks are user-defined shell commands that execute at various points in Claude Code’s lifecycle. Hooks provide deterministic control over Claude Code’s behavior, ensuring certain actions always happen rather than relying on the LLM to choose to run them. For reference documentation on hooks, see Hooks reference.

Hooks communicate status and control flow through exit codes: ... Hook executed successfully. stdout shown to user in transcript mode (Ctrl-R) ... Critical: stderr is fed back to Claude automatically.

July 1, 2025 - How do you enable this? I had a look here but couldn’t find it (unless I missed it) https://docs.anthropic.com/en/docs/claude-code/settings ... I changed my whole workflow to spec-driven using UserPromptSubmit Event and Stop hooks.

Real-time monitoring and visualization for Claude Code agents through comprehensive hook event tracking.

July 2, 2025 - This article serves as a comprehensive guide to understanding, configuring, and leveraging Claude Code Hooks to create a fully automated and streamlined development workflow. At their core, Claude Code Hooks are user-defined shell commands that execute automatically at specific points in Claude Code’s lifecycle.

July 8, 2025 - Claude Code has introduced hooks that now automate your workflow in a way similar to triggers — executing automatically at specific points

We cannot provide a description for this page right now

July 1, 2025 - That means I can write a custom hook that’s more dynamic than just running jj commit. After about 5-10 minutes of using my human brain, here’s what I wrote. Take a moment to use your human brain to read and understand the code. It’s quite trivial since I was in discovery mode here to see how this all works. package main import ( "bufio" "encoding/json" "fmt" "os" "os/exec" ) // StopHookInput is the input that Claude Code sends during a Stop hook event.

Claude Code Hooks are callback functions that execute at specific lifecycle events during Claude's agent loop.

November 4, 2025 - { "hooks": { "PreToolUse": [ { "matcher": "Edit|MultiEdit|Write", "hooks": [ { "type": "command", "command": "but claude pre-tool" } ] } ], "PostToolUse": [ { "matcher": "Edit|MultiEdit|Write", "hooks": [ { "type": "command", "command": "but claude post-tool" } ] } ], "Stop": [ { "matcher": "", "hooks": [ { "type": "command", "command": "but claude stop" } ] } ] } } Essentially, you want to run the but claude pre-tool command before any code generation or editing, and the but claude post-tool command after it.

September 30, 2025 - Explore our complete guide to hooks in Claude Code. Learn what they are, how they work, and their limitations for true business workflow automation.

February 28, 2025 - Let me hook into the lifecycle of the agent(s) execution. As an MVP, when CC completes a task. I'm aware that this might be counter intuitive with agentic behaviors and the developer goals. But there are simple and high value efficiencie...

October 7, 2025 - What are Claude Code Hooks? Claude Code hooks are automated scripts that run at specific points in Claude Code’s lifecycle. They allow you to: Hook...

August 3, 2025 - Think of hooks as little event listeners that let you run custom scripts when specific things happen in Claude Code.

1 month ago - You’ve configured your PostToolUse hook to auto-format on every file write. It worked… once. Now Claude Code ignores it completely, and you’re back to manually running Prettier.

This page provides reference documentation for implementing hooks in Claude Code.