Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

Hook event names gain a wildcard/negation pattern grammar and a 'classic.' namespace

Hook event names now support wildcard and negation patterns, and internal plugin hooks are namespaced as classic.<EventName>

TierUse it nowhow much it should matter to you
Useful4my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaHookswhat it touches
KindImprovementsin v2.1.265,
Use it now Notable

Hook event names now support wildcard and negation patterns, and internal plugin hooks are namespaced as classic.<EventName>

What

Hooks (scripts that run automatically at points like PreToolUse, before a tool call executes) can now be registered against event name patterns, not just exact names. A pattern can be * (matches everything), <prefix>.* (matches everything under a prefix), or either form prefixed with ! to negate it. Separately, internally-defined plugin hook events are now namespaced with a classic. prefix, so PreToolUse becomes classic.PreToolUse internally.

Why

Wildcard and negation patterns let a single hook registration cover a group of related events instead of listing each one individually. The classic. namespace distinguishes built-in plugin hook events from other event sources as the hook system grows more general.

See this entry in the whole of v2.1.265 →

Feedback