Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.239 ·

Marketplaces can list plugins by bare name under metadata.pluginRoot

Marketplaces can set metadata.pluginRoot so plugin entries resolve by bare name inside one folder.

Use it now New Features
JSON All of v2.1.239
Use it nowTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
New FeaturesKind: in v2.1.239,
What probably matters to youSection of the release
What

A plugin marketplace file can now declare metadata.pluginRoot once at the top, and entries whose source is a bare name (not a ./relative/path) are resolved inside that folder. If pluginRoot is absent, or points outside the marketplace directory, the entry loads as a stub carrying an explanatory error rather than failing quietly.

Details
  • Applies only to bare source names; relative paths behave as before.
  • pluginRoot must itself be a relative path contained by the marketplace root.
  • No gate: this is plain marketplace loading.
Evidence

Bare source names resolve under metadata.pluginRoot

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundlemetadata.pluginRoot
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed marketplace metadata.pluginRoot having no effect: bare plugin source names now resolve under it as the docs describe

See this entry in the whole of v2.1.239 →

Feedback