{"version":"2.1.239","anchor":"plugin-commands-explain-why-a-plugin-cannot-be-toggled","canonical_anchor":"plugin-commands-explain-why-a-plugin-cannot-be-toggled","heading":"Plugin commands explain why a plugin cannot be toggled","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/plugin-commands-explain-why-a-plugin-cannot-be-toggled","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Plugin commands explain why a plugin cannot be toggled\n\nPlugin commands now explain refusals for built-ins and org-locked plugins instead of acting oddly.\n\n**What**\n\n`claude plugin enable`, `disable`, `install`, `update` and `uninstall` now refuse clearly instead of acting confusingly. Built-in plugins can only be enabled or disabled, never installed, updated or uninstalled, and a plugin locked by organization managed settings cannot be toggled for a `--plugin-dir`, skills directory or claude.ai-synced copy.\n\n**Details**\n\n- Toggling a synced plugin now reports when a higher-precedence settings source would still govern it, or when `--setting-sources` makes the session ignore that source.\n- `disable-all` now writes explicit false entries for synced plugins that no settings file mentions.\n\n**Evidence**\n\n`built-in plugins cannot be installed, updated or uninstalled`\n\n- Area: Plugins\n- Names: `claude plugin enable`, `claude plugin disable`, `claude plugin install`, `claude plugin update`, `claude plugin uninstall`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}