What
/plugin opens the menu for managing plugins, the add-ons that extend Claude Code. Each time you enable, disable or uninstall a plugin there, Claude Code now records the action, the plugin, and its scope (where the setting applies, such as your user or a project). Uninstalls also note whether saved data was kept. Marketplace names are also tidied up before they are shown.
Why
Plugin changes made in the menu are now tracked.
Names in the bundle/plugin
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up /plugin, on Configure permissions.
That precedence covers hooks in settings files and in a plugin's `hooks/hooks.json`. A [mod](/docs/en/plugins/mods/overview) you install that hooks `tool.check` answers after the rules and the `PreToolUse` hooks have decided, and its answe…permissions see the edit
Added since
A small documentation edit on Explore the .claude directory touched a line naming /plugin after this was published.
| `dev-mods/<session>/` | [Mods that Claude wrote](/docs/en/plugins/mods/create#ask-claude-for-a-mod) during the session |claude-directory see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear whether the record is usage reporting sent elsewhere or state kept on your computer.
Anthropic's documentation agrees
A small documentation edit on Explore the .claude directory touched a line naming /plugin after this was published.
Anthropic's release notes agree
Fixed /plugin's Discover tab showing a marketplace name unquoted in its "Checking … for new plugins" line when its rows already show that…