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
HomeReleasesv2.1.246entry #57

Claude Code v2.1.246 ·

Plugin provenance can be supplied via CLAUDE_CODE_PLUGIN_ATTRIBUTION

You can declare where a plugin came from via a JSON file or an environment variable.

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

Claude Code can now read where a plugin came from, either from a JSON file placed next to the plugin or from a map in the CLAUDE_CODE_PLUGIN_ATTRIBUTION environment variable. It yields a server-side plugin id (plugin_ plus letters and digits), a marketplace name and an installation preference. The variable is unset by default, and it is now stripped from the environment handed to spawned subprocesses so it does not leak into tools.

Details
  • Malformed input is ignored with a warning rather than failing plugin load, for example when the value is not a JSON object.
  • Presence of the variable is itself a reason to build a scrubbed child environment before spawning.
Evidence

Ignoring CLAUDE_CODE_PLUGIN_ATTRIBUTION: not a JSON object

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

Read from
Names in the bundleCLAUDE_CODE_PLUGIN_ATTRIBUTION
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_PLUGIN_ATTRIBUTION

See this entry in the whole of v2.1.246 →

Feedback