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 ·

Plugin tool.check hooks get an extra input when a PreToolUse hook asks for permission

When a PreToolUse hook has asked for permission, plugin tool checks are now built with that hook's ask passed in as an extra input

Under the hood Improvements
JSON All of v2.1.289
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Plugin HooksArea: what it touches
ImprovementsKind: in v2.1.289,
ImprovementsSection of the release
What

Plugins can define a tool.check hook, a piece of plugin code that looks at a tool call before it runs. A tool call is Claude Code using one of its tools, such as running a shell command or editing a file. When a PreToolUse hook has asked for permission, Claude Code now builds the plugin's tool.check with that ask passed in as an extra input. A PreToolUse hook is a hook that runs before a tool call executes and can block it. Previously the check was built without this input.

Why

This changes how plugin tool checks and permission requests from hooks fit together. If you use both, a plugin's check can now be affected by an earlier hook's request to ask you first.

Read from
Names in the bundletool.checkPreToolUse
What the documentation says
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 doubtWhat the plugin check does with the hook's ask is not clear.

See this entry in the whole of v2.1.289 →

Feedback