Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.242 ·

Each hook event enforces what a plugin is allowed to change

Plugin hooks are limited in what they may rewrite, and cannot take over question prompts.

Nothing to try yet In Development
JSON All of v2.1.242
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
PluginsArea: what it touches
In DevelopmentKind: in v2.1.242,
What probably matters to youSection of the release
What

Return values from a hook are validated per event rather than trusted. A subagent spawn hook may only rewrite the model. A pre-tool-use hook must keep the tool envelope's keys intact. A prompt submission hook may return replacement text or a drop string. The question component is refused as a render target outright, because its answer authorises an action; a plugin can add context around it with a notice instead.

Details
Evidence

is drawn by the engine alone; its answer authorises an action. A plugin adds context with $.ui.notice

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.242 →

Feedback