What
claude plugin enable and claude plugin disable now register built-in plugins first, so bundled plugins can be enabled or disabled by name. Their counters are awaited before the process exits, where previously events could be dropped by the immediate exit.
Details
plugin installnow routes thrown errors through the shared error handler.- The shared handler gained an
enablecase emitting a dedicated failure code,cli_plugin_enable_failed. - No gate.
Evidence
cli_plugin_enable_failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleclaude plugin enableclaude plugin disable
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 claude plugin disable, on Plugins reference.
* **Turn one off**: in the synced session, run `claude plugin disable <name>@synced`, or ask Claude to run it. Claude Code saves the choice as `"<name>@synced": false` in that environment's user-level [`enabledPlugins`](/docs/en/settings-r…plugins-reference see the edit
Confirmed since
Anthropic's documentation has since written up claude plugin enable, on Plugins reference.
* **Turn one off**: in the synced session, run `claude plugin disable <name>@synced`, or ask Claude to run it. Claude Code saves the choice as `"<name>@synced": false` in that environment's user-level [`enabledPlugins`](/docs/en/settings-r…plugins-reference see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up claude plugin enable, on Plugins reference.