Source Intelligence

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.213 Home All releases olderv2.1.212 v2.1.214newer
Claude Code v2.1.213

SDK Protocol: Plugin Version Field

What

Plugins now expose their version as declared in plugin.json through the SDK wire format.

Details
  • The version string is emitted verbatim from the plugin manifest (plugin-author-controlled — validate before trusting)
  • Omitted when the manifest declares no version
  • The version field appears in the plugins array in two SDK message types: the system:init message (sent at session startup listing all loaded plugins) and the reload_plugins engine-control response (sent after a plugin reload)
  • In both locations the field is typed as S.string().optional(), so hosts must handle its absence for plugins that omit a version in their manifest
  • A separate plugin_version attribute is also recorded in telemetry events for marketplace-approved plugins when a skill command is invoked, enabling per-version usage metrics on the server side; third-party plugins emit "third-party" as the repository sentinel and no version is sent to telemetry
Evidence

Schema addition (search for "The plugin's version as declared in its plugin.json manifest, emitted verbatim"); wire positions (search for u7a used in system:init plugins array and reload_plugins response schema)

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.213 →