You can declare where a plugin came from via a JSON file or an environment variable.
What's wrong with this entry?
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.
- 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.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Attribution header can override the environment opt-out
Both mention attribution
-
v2.1.229
Auto-mode side queries always send the billing attribution header
Both mention attribution
-
v2.1.227
Billing attribution header carries a prompt id and validates its values
Both mention attribution