What it is
Plugin hooks can now react to tool-call dry-runs, config changes, and session attach/detach events.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.269.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
First cited
4The earliest release whose published evidence quoted plugin.register was v2.1.269, 11 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table above.
Names beside it
Every settings key in the inventory starting plugin, up to twelve of them.
plugin.jsonSkill listing and job tracking now go through the storage layer instead of touching files directly. never mined
pluginConfigsStore the answers you gave a [plugin](/docs/en/plugins)'s configuration dialog v2.1.138
pluginDeliveryA new SDK option lets plugins be delivered via the initialize request instead of argv, still opt-in. never mined
pluginsSigning in can request an extra permission for plugin search, though search itself remains policy-gated. never mined
pluginSuggestionMarketplacesChoose which [marketplaces](/docs/en/plugin-marketplaces#managed-marketplace-restrictions) can surface plugin install suggestions in /plugin v2.1.152
pluginTrustMessageAdd your own text to the [plugin](/docs/en/plugins) trust warning v2.1.138
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.