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.296 ·

Plugin dependencies handle same-name plugins synced from claude.ai

Plugin dependency matching now accounts for same-name plugins synced from your claude.ai account, and its errors explain the conflict and how to fix it

Group of 2 You'll notice Improvements
JSON All of v2.1.296
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.296,
ImprovementsSection of the release

What

Plugins are add-ons for Claude Code, and a plugin can depend on another plugin. Some plugins come from a marketplace synced from your claude.ai account. This release changes how dependencies are matched when a plugin with the same name is involved:

  • Matching: a dependency on name@<synced marketplace> is now accepted when the plugin declaring it also comes from the synced marketplace. Before, dependencies resolved only against the exact id or the default marketplace suffix.
  • Error text: when a dependency is reported as not installed but a same-name plugin is loaded from your claude.ai account, the error carries a sameNameSyncedPlugin hint and says that copy "is loaded from your claude.ai account but meets a marketplace dependency only for other claude.ai plugins".
  • Fix hint: the suggestion now reads Install "X", which then loads instead of "Y", or .... It used to read Install "${dependency}" or uninstall "${plugin}".
  • Disable instead of uninstall: for plugins from a claude.ai-synced marketplace, the hint now says to disable the plugin rather than uninstall it.

Why

If you use plugins synced from claude.ai, a confusing "not installed" error now explains which copy is loaded and what to do. Dependencies between synced plugins that failed to resolve before should now resolve.

See this entry in the whole of v2.1.296 →

Feedback