Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

Plugin hook error handlers survive a restart of the hooks worker

If the worker running plugin hooks is replaced mid-event, Claude Code now waits for the new one and lets the plugin's error handler run there

You'll notice Bug Fixes
JSON All of v2.1.290
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
Bug FixesKind: in v2.1.290,
Bug FixesSection of the release

Unclear It is not clear whether plugin hook modules are themselves behind a switch.

What

Hooks are pieces of code that run when something happens in Claude Code, such as a tool being used. Plugin hooks run in a separate background process called the hooks worker. If that worker ends or is replaced partway through an event, Claude Code now waits for the replacement and runs the plugin's error handler (its .catch) there. Before, the failure simply passed through.

Other changes to hooks:

  • Text a hook writes to the log is now shortened
  • Claude Code now records which tool a hook ran for, and whether it ran for account memory
  • Claude Code now records when a hook starts in the folder Claude Code was launched from
Why

Plugin hooks are less likely to fail outright just because their worker restarted.

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 doubtIt is not clear whether plugin hook modules are themselves behind a switch.

See this entry in the whole of v2.1.290 →

Feedback