Plugin resolution now distinguishes 'sync-attributed' plugins, which carry attributedMarketplaceName, serverPluginId, and installationPreference, from plain --plugin-dir copies. Each is checked against managed settings through a new admission function, and duplicate managed-plugin claims across session and synced copies are dropped. When an organization's managed settings restrict to hooks-only via allowManagedHooksOnly, admitted-by-lock plugins are now tagged with a managed-hooks-restricted warning.
Names in the bundleallowManagedHooksOnly
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.
Added since
A small documentation edit on Customize your status line touched a line naming allowManagedHooksOnly after this was published.
The same trust, `disableAllHooks`, and [`allowManagedHooksOnly`](/docs/en/settings-reference#allowmanagedhooksonly) gates that apply to `statusLine` apply here. Plugins can ship a default `subagentStatusLine` in their [`settings.json`](/do…statusline see the edit
Confirmed since
Anthropic's documentation has since written up allowManagedHooksOnly, on MCP, plugins, skills, and hooks.
Claude Code [managed settings](/docs/third-party/claude-desktop/code#interaction-with-claude-code%E2%80%99s-own-managed-settings) deployed on the device govern these hooks as they do in the Claude Code CLI: `disableAllHooks` turns them off…third-party/claude-desktop/extensions see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up allowManagedHooksOnly, on MCP, plugins, skills, and hooks.