YOU ARE VIEWING ONE ITEM FROM THE AICRIER FEED

Claude Code 2.1.295 makes hooks fail closed

AICrier tracks AI developer news across Product Hunt, GitHub, Hacker News, YouTube, X, arXiv, and more. This page keeps the article you opened front and center while giving you a path into the live feed.

// WHAT AICRIER DOES

7+

TRACKED FEEDS

24/7

SCRAPED FEED

Short summaries, external links, screenshots, relevance scoring, tags, and featured picks for AI builders.

Claude Code 2.1.295 makes hooks fail closed
OPEN LINK ↗
// 1h agoPRODUCT UPDATE

Claude Code 2.1.295 makes hooks fail closed

Claude Code 2.1.295 adds `onFailure: "block"` for command and HTTP hooks, so missing executables, timeouts, and unexpected failures block guarded actions instead of allowing them through. The opt-in change strengthens policy enforcement while preserving fail-open behavior for existing hooks.

// ANALYSIS

This is a small configuration switch with outsized operational impact: policy hooks only work as controls when their own failures are treated as denials.

  • –Use it for deterministic gates protecting secrets, deployments, destructive commands, or compliance checks.
  • –Leave logging, formatting, and notification hooks fail-open so transient outages do not halt development.
  • –Existing hooks retain the `continue` default, so teams must explicitly add `onFailure: "block"` and test broken paths and timeouts.
  • –The setting applies to command and HTTP hooks; it complements, rather than replaces, Claude Code’s permissions and sandboxing.
// TAGS
claude-codeai-codingcoding-agentguardrailssecurityclidevtool

DISCOVERED

1h ago

2026-10-11

PUBLISHED

1h ago

2026-10-11

RELEVANCE

9/ 10

AUTHOR

DIY Smart Code