Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.286 ·

Plugin hook if conditions now match differently for some plugins

A hook's if condition now checks whether a command hook comes from a plugin that is specially marked, which can change what the condition matches

Under the hood Internal Changes
JSON All of v2.1.286
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.286,
Internal ChangesSection of the release
What

A hook is a command that Claude Code runs automatically at set moments, such as before a tool is used, and a hook can carry an if condition that decides when it fires. The way that condition is matched now takes one more input. That input is true only for command hooks that come from a plugin, and only when that plugin is marked in a particular way.

  • The rule matching behind if conditions now treats a rule with specific content as a match when that input is true.
  • The check against deny rules now returns a fallback answer when it cannot judge a case, instead of deciding on its own.
Why

For hooks that come from plugins, an if condition may now match in cases where it did not before, so such a hook can fire more often.

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 what marks a plugin for this treatment or who sets that mark.

See this entry in the whole of v2.1.286 →

Feedback