Follow Discord
Sweep 03 Oct 2026 · 20:28Z Build v2.1.289 510 read Stable v2.1.285 Latest v2.1.289 Next v2.1.289 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.289 ·

Warnings for plugin hooks that were not applied no longer say "skipped"

A plugin hook that was not applied now gets a warning reading "<event> hook: <reason>" instead of "<event> hook skipped: <reason>"

You'll notice Improvements
JSON All of v2.1.289
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Plugin HooksArea: what it touches
ImprovementsKind: in v2.1.289,
ImprovementsSection of the release
What

When a plugin hook is not applied, Claude Code's warning now reads <event> hook: <reason>, for example naming the event such as PreToolUse. A hook is plugin code that runs at a certain moment, such as before a tool runs. Previously the warning said <event> hook skipped: <reason>. Other hook warnings still say "skipped". Claude Code avoids showing the same warning twice, and the label is now part of how it tells warnings apart.

Why

The wording is more accurate for a hook that was not skipped but simply not applied.

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 doubtWhen a hook counts as not applied rather than skipped is not stated.

See this entry in the whole of v2.1.289 →

Feedback