What
The command that disables all plugins now handles two more cases:
- Plugins enforced by managed settings, which an administrator controls, count as required and are skipped. Before, only plugins the organization required were skipped.
- When plugins stay enabled because the
--settingsoption keeps them on, the result says they are still enabled this session.
Why
The result message now explains why some plugins stayed on, so you are not left wondering why the command seemed to miss them.
--settings
Error reference modified, high confidence
Claude Code found a `Write`, `NotebookEdit`, `MultiEdit`, or `Glob` [permission rule](/docs/en/permissions#read-and-edit) with a path in one of your [settings files](/docs/en/settings#where-settings-live), in [managed settings](/docs/en/ma…see the edit
--settings
Manage multiple agents with agent view modified, high confidence
1. The target directory's [`permissions.defaultMode`](/docs/en/settings-reference#permissions-defaultmode). `auto` and `bypassPermissions` [take effect only from managed settings, a `--settings` file, or `~/.claude/settings.json`](/docs/en…see the edit
--settings
Choose a permission mode modified, high confidence
If [`claude agents`](/docs/en/agent-view#dispatch-defaults) shows the [bypass permissions warning](#bypass-permissions-acceptance) although your interactive sessions skip it, check whether `skipDangerousModePermissionPrompt` is set in `.cl…see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
--settings on Error reference
Anthropic's release notes agree
Changed the axScreenReader setting and CLAUDE_AX_SCREEN_READER in a settings env block to apply only from user, managed or --settings…