Tag: hooks

Since Claude Code v2.1.295, a command or HTTP hook can set onFailure to "block" so a guard that crashes, times out, cannot start or prints invalid JSON stops the tool call instead of waving it through. Here is the config, what counts as a failure, the events where it does nothing, and the exit-0 trap no setting can catch.

A coding agent refactors a component, renames a data-testid, and your Playwright suite goes red. Here is a three-layer setup, verified on Playwright 1.63.0 and Claude Code 2.1.197: locators that survive, a PreToolUse hook that blocks the rename, and a CI guard that lets the Playwright healer agent fix locators but never rewrite an assertion.

Claude Code 2.1.274 still loads only CLAUDE.md. Bridge AGENTS.md with an @AGENTS.md import or a symlink, then avoid the three traps: imports that don't expand from a subdirectory, symlinks that Windows checks out as a 9-byte text file, and Edit refusing to write through the link. Includes a CI check and a SessionStart hook for repos you don't own.

Since Claude Code 2.1.77 a PreToolUse hook's allow cannot override a deny or ask rule. Find the matching rule with /permissions, then move the policy into the hook.

When a Stop hook, /goal condition, or CI-style gate demands a check the agent's environment can never pass, Claude Code keeps re-running it until the 8-consecutive-block cap (2.1.143+) ends the turn. Here is why it happens and the hook patterns that let the agent give up correctly.