Unclear It is not clear whether Claude Code's behaviour changed or only the description of the setting.
What
allowManagedPermissionRulesOnly makes managed settings (settings an organization's administrator sets centrally) the only place permission rules can come from. Its handling of plugins (add-on packages) changed.
- One check on whether a plugin's source is trusted now also fails when managed settings set
allowManagedPermissionRulesOnlyto true and Claude Code is in a managed mode. - The setting's description now says plugins delivered by the host app through
--plugin-dirkeep theirallowed-tools(tools they may use without asking) only in Claude Desktop, and only while the setting is not set by the organization's own managed settings. Before, it said these plugins kept theirallowed-toolswith no such condition.
Why
In organizations that turn this setting on, some plugins may no longer be treated as trusted, and Desktop plugins loaded with --plugin-dir may need to ask before using tools they previously used freely.
Names in the bundleallowManagedPermissionRulesOnly--plugin-dir
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 --plugin-dir, on Plugin loading reference.
For how to write `--plugin-dir` and skills-directory plugins, see [Create plugins](/docs/en/plugins/create).plugins/loading see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear whether Claude Code's behaviour changed or only the description of the setting.
Anthropic's documentation agrees
Anthropic's documentation has since written up --plugin-dir, on Plugin loading reference.
Anthropic's release notes agree
Changed plugins that Claude Desktop mounts by path to no longer keep their allowed-tools when your organization's managed settings set…