{"version":"2.1.26","anchor":"plugin-disable-all-flag","canonical_anchor":"plugin-disable-all-flag","heading":"Plugin Disable --all Flag","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.26\/e\/plugin-disable-all-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.26","markdown":"### Plugin Disable --all Flag\n\n**What**\n\nThe `claude plugin disable` command now accepts an optional `--all` flag to disable all enabled plugins at once, instead of requiring a specific plugin name.\n\n**Usage**\n\n`claude plugin disable --all claude plugin disable [plugin]` **Details** - The command signature changed from `disable <plugin>` (required) to `disable [plugin]` (optional) - Use `--all` \/ `-a` to disable all enabled plugins in one shot - Cannot combine `--all` with a specific plugin name (error: \"Cannot use --all with a specific plugin\") - Cannot combine `--scope` with `--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\"`)"}