Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.321 ·

Plugins can now make tool permissions stricter, but never looser

A new tool.check hook lets plugins answer allow, deny or ask on a tool check, and only stricter answers take effect for built-in tools

Use it now Notable New Features
JSON All of v2.1.321
Use it nowTier: how much it should matter to you
5Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
PluginsArea: what it touches
New FeaturesKind: in v2.1.321,
What probably matters to youSection of the release

Unclear Whether the plugin system that runs this hook is switched on by default is not known.

What

Plugins can now take part in permission checks through a new tool.check hook. A plugin is an add-on that extends Claude Code. A hook is an event that a plugin can respond to. When Claude Code checks whether a tool may run, a plugin can now answer allow, deny or ask.

For built-in tools and some MCP tools, Claude Code limits what a plugin's answer can do. MCP tools are tools that come from outside services connected to Claude Code. For these tools Claude Code ignores:

  • any allow answer from a plugin
  • any plugin answer at all when Claude Code's own permission check has already denied the tool

When Claude Code ignores a plugin's answer, it records that it kept its own decision, and that plugins can only make that tool's permission stricter in this session.

Why

Plugins now have a way to add extra caution to tool use, such as asking first or blocking a tool. They cannot use this hook to quietly grant a built-in tool more access than your own permission settings give it.

Read from
Names in the bundletool.check
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 doubtWhether the plugin system that runs this hook is switched on by default is not known.

See this entry in the whole of v2.1.321 →

Feedback