Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

Plugin install no longer accepts npm packages or the --registry option

The plugin install command no longer handles <package>@npm specs or the --registry option, and it has new failure codes

You'll notice Removed
JSON All of v2.1.323
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PluginsArea: what it touches
RemovedKind: in v2.1.323,
RemovedSection of the release

Unclear Whether installing plugins from npm is still possible some other way in this release is not clear.

What

Plugins are add-on packages for Claude Code. The plugin install command no longer handles these:

  • <package>@npm specs, which installed a plugin from the npm package registry
  • the --registry <url> option, which chose a different npm registry for such an install
  • the check that the --registry value is an http or https address

Install can also now stop with a new failure code, engine_range, and can report a failure code of builtin or directory_loaded.

Why

If you installed plugins from npm, or pointed install at your own npm registry with --registry, that no longer works through this install command.

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 installing plugins from npm is still possible some other way in this release is not clear.

See this entry in the whole of v2.1.323 →

Feedback