Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.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

TierUse it nowhow much it should matter to you
Useful3my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaHookswhat it touches
KindNew Featuresin v2.1.275,
Use it now Notable No documentation found

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

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 →