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 ·

Plugin tool calls skip the auto-mode classifier and are refused if they need a person's approval

Tool calls a plugin makes now skip auto mode's classifier when plugin policy allows them, and are refused when they would need a person's approval

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

Unclear Whether plugin tool calls now end up allowed or asked more often than before is not shown.

What

A plugin is an add-on that extends Claude Code, and it can make tool calls of its own. A tool call is one action, such as running a command or editing a file. Auto mode is a setting where a safety classifier, a check run by a model, decides whether to allow actions instead of asking you. How plugin-made calls are handled has been reworked:

  • A plugin call is allowed only if nothing requires asking for approval. Allowed calls carry the reason plugin-origin: ${h}.
  • If the call would need approval, it is refused with the message "wasn't run: this call needs a person's approval, and a mod's own call can't ask for it."
  • In auto mode, when plugin policy allows a plugin call, the classifier is skipped. Claude Code logs Skipping auto mode classifier for ${e.name}: called by plugin ${xe}. This replaces the old pluginOrigin allow branch.
  • Ask rules served by hooks or set by your organization are still honored.
  • A separate harnessSynthesized fast path handles calls that Claude Code itself generated through its observer check, with the reason harness-synthesized: ${H.synthesizedBy}.

Before, the old helper either gave a pluginOrigin allow decision with the reason plugin-origin: ${pl}, or returned the ask decision when an internal flag was set.

Why

A plugin's own call has no person behind it to answer an approval prompt. So instead of waiting on a question nobody will see, such a call is now refused outright when it needs approval. When it is allowed, it no longer goes through the auto-mode classifier. If a plugin action you expected does not run, this message tells you it needed approval that a plugin cannot ask for.

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 plugin tool calls now end up allowed or asked more often than before is not shown.
Anthropic's release notes agree[VSCode] Fixed a plugin's permission request showing a name with hidden characters: it now reads "a plugin"

See this entry in the whole of v2.1.321 →

Feedback