What probably matters to youSection of the release
Unclear Nothing has been read yet about whether the tengu_plugins_npm_marketplace gate is switched on for any account.
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 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.
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.
