Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.275entry #4

Claude Code v2.1.275 ·

Plugins can now be installed and updated directly from the npm registry

Claude Code plugins can now come from npm packages, not just git or the marketplace, behind a gate

Group of 6 Use it now Notable Nothing to try yet In Development
JSON All of v2.1.275
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
In DevelopmentKind: in v2.1.275,
What probably matters to youSection of the release

What

  • Plugin installs and updates can now use an npm registry as the source, alongside the existing git and claude.ai sources. Install records track npmVersionSpec, npmResolved, npmIntegrity, and npmRegistry, and installation refuses to proceed if the package's integrity can't be verified.
  • Plugin identifiers can now reference npm-scoped packages, such as @scope/name, and @scope/name@npm is understood as that package sourced from npm.
  • claude plugin install recognizes an @npm-suffixed spec (name@npm, @scope/name@npm, name@1.2.3@npm) and a new --registry option to install straight from a given npm registry URL, bypassing the marketplace system entirely.
  • A deep link (claude://install-plugin) can now install a plugin directly, taking a plugin name and an optional marketplace, which can also point at an npm source.
  • This whole capability is gated behind an account flag and a feature gate (tengu_plugins_npm_marketplace).

Why

This lets teams distribute and install plugins as ordinary npm packages instead of requiring a git-based marketplace, while still verifying the downloaded package's integrity before trusting it.

Read from
Names in the bundle--registry/plugin install
Feature flag
tengu_plugins_npm_marketplace Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.275: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.275. It isn't a statement about your account. What a flag value here can and cannot tell you

What the documentation says
Documented inmcp/registry/about
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Week 33 · August 10–14, 2026 touched a line naming /plugin install after this was published. <div><a href="/docs/en/plugins/install#install-a-plugin"><code>/plugin install plugin\@marketplace</code></a> refreshes the marketplace first, so newly published plugins install without a manual marketplace update</div> whats-new/2026-w33 see the edit
Confirmed since Anthropic's documentation has since written up /plugin install, on Error reference. You confirmed adding a marketplace through [`/plugin install <plugin> --marketplace <source>`](/docs/en/discover-plugins#add-a-marketplace-and-install-in-one-command), and the catalog Claude Code fetched from that source names itself the s… errors see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /plugin install, on Error reference.
Anthropic's release notes agreeAdded /plugin install <plugin> --marketplace <source>, which offers to add the marketplace before installing the plugin
The name it cites is new in this buildNew in this build: --registry

See this entry in the whole of v2.1.275 →

Feedback