Follow Discord
Sweep 28 Sep 2026 · 18:16Z Build v2.1.284 505 read Stable v2.1.277 Latest v2.1.284 Next v2.1.284 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.284 ·

Hooks from a plugin on an unavailable machine now fail with a clear message

Hooks from a plugin that runs on another machine now report that the machine is unavailable, instead of failing with an unexplained error

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

Hooks are commands that run at set moments, such as before a tool runs. Some plugins run their hooks on another machine. When that machine is not available, the hook now fails with the message "This plugin's hooks run on another machine, which is not available."

  • For events that can block an action, including PreModelSwitch, the hook blocks, just as a hook returning exit status 2 would.
  • For other events, the hook is treated as having failed to start.
Why

You get an explanation of why the plugin's hooks did not run, instead of an unexplained error.

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 makes a plugin's hooks run on another machine.

See this entry in the whole of v2.1.284 →

Feedback