Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.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>

Use it now Notable Improvements
JSON All of v2.1.265
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.265,
What probably matters to youSection of the release
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