Claude Code plugins can now come from npm packages, not just git or the marketplace, behind a gate
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, andnpmRegistry, 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@npmis understood as that package sourced from npm. claude plugin installrecognizes an@npm-suffixed spec (name@npm,@scope/name@npm,[email protected]@npm) and a new--registryoption 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 apluginname and an optionalmarketplace, 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.
tengu_plugins_npm_marketplace Not enough to sayNothing 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
Nothing has been read yet about whether the `tengu_plugins_npm_marketplace` gate is switched on for any account.
New in this build: --registry