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.269 ·

Plugin hooks-module scan enforces that next.to() targets be statically discoverable

Plugins that call next.to() with a hooks module name Claude Code can't find in the code are now rejected

Under the hood Bug Fixes
JSON All of v2.1.269
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Plugin HooksArea: what it touches
Bug FixesKind: in v2.1.269,
Bug FixesSection of the release
What

Plugin code can call next.to("name") to hand off to a named hooks module (a plugin file that reacts to Claude Code events). A new check now scans plugin code ahead of time to make sure that name is spelled out literally somewhere it can find. If the target can't be located this way, the call now throws an error instead of proceeding.

Why

This closes off hooks-module handoffs that can't be verified in advance, which previously could fail unpredictably at runtime. Plugin authors need to name next.to() targets literally so the static scan can find them.

Read from
Names in the bundlenext.to
What the documentation says

See this entry in the whole of v2.1.269 →

Feedback