You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
Bug FixesKind: in v2.1.284,
Bug FixesSection of the release
What
A plugin can list other plugins it depends on. A dependency can be written as a bare name, or with @marketplace added to say which marketplace it comes from.
A dependency given as a bare name is now satisfied by an enabled plugin of that name from a marketplace, and Claude Code resolves it to that specific plugin. Before, a bare dependency was checked only by counting plugins with that name. Claude Code also now puts plugin names in a consistent form before comparing them, including when it reads enabledPlugins, the setting that turns plugins on or off. Before, enabledPlugins was matched on the exact name only.
Why
This should stop false "dependency not found" errors for plugins that name their dependencies without a marketplace, when the plugin they need is installed and enabled.
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 doubtIt is not clear exactly how plugin names are rewritten into a consistent form before they are compared.
