What's wrong with this entry?
Anonymous. No account, no email.
What
The claude plugin disable command now accepts an optional --all flag to disable all enabled plugins at once, instead of requiring a specific plugin name.
Usage
claude plugin disable --all
claude plugin disable [plugin]Details
- The command signature changed from
disable <plugin>(required) todisable [plugin](optional) - Use
--all/-ato disable all enabled plugins in one shot - Cannot combine
--allwith a specific plugin name (error: "Cannot use --all with a specific plugin") - Cannot combine
--scopewith--all - If no plugins are enabled, displays "No enabled plugins to disable"
Evidence
Plugin disable all handler (search for "Disable all enabled plugins" or "Cannot use --all with a specific plugin")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.