Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.193 Home All releases ←olderv2.1.191 v2.1.195newer→
Claude Code v2.1.193

Plugin Renaming in Marketplace Manifests

What

Marketplace authors can now declare plugin renames in their manifest using a renames field. When a plugin is not found under its old name, Claude Code follows the rename chain and migrates the user's settings to the new name automatically.

Details
  • The renames field is an append-only map of old plugin name → current name (or null to indicate the plugin was removed).
  • On plugin-not-found, the loader resolves the chain and updates enabledPlugins and pluginConfigs in all writable settings files.
  • A new tengu_plugin_renamed telemetry event tracks rename outcomes (resolved, removed, unresolved).
  • Unresolvable renames (cycles, missing targets, chains deeper than the limit) are logged with the reason.
Evidence

New renames schema field (search for "Append-only map of old plugin name") and rename migration logic (search for "migrateRenamedPluginsInSettings")

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

See this entry in the whole of v2.1.193 →