Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.275 ·

Hooks can be disabled per-agent via settingsHooksOff

A new settingsHooksOff option can disable all hook execution for a given agent or subagent run

Use it now Notable No documentation found New Features
JSON All of v2.1.275
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
New FeaturesKind: in v2.1.275,
What probably matters to youSection of the release

Unclear The finding doesn't say what user-facing setting or scenario sets settingsHooksOff, so how a user would trigger this isn't clear.

What

Several internal functions responsible for assembling and running hooks (user-configured scripts that run at specific points, including agent-context hooks) now check for a new settingsHooksOff option. When it's set to true, they short-circuit and skip running any hooks entirely for that agent or subagent run.

Why

This provides a way to fully disable hook execution for a specific run, which is useful for situations where hooks shouldn't fire, such as isolated or internal subagent invocations.

Read from
Names in the bundlesettingsHooksOff
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding doesn't say what user-facing setting or scenario sets `settingsHooksOff`, so how a user would trigger this isn't clear.

See this entry in the whole of v2.1.275 →

Feedback