What
Claude Code's check for whether to restrict hooks (small scripts that run automatically at certain points) to only the ones an organization manages now also returns true based on a new internal condition, BJ(), in addition to the existing allowManagedHooksOnly policy setting. BJ() looks at whether any hooks currently exist.
Why
This adds another path that can trigger managed-hooks-only mode beyond the explicit organization policy setting, though the finding does not say what user-facing behavior results.
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 Set up Claude Code for your organization.
| [Hook restrictions](/docs/en/settings-reference#allowmanagedhooksonly) | Restrict which hooks run and restrict HTTP hook URLs; see [what runs under `allowManagedHooksOnly`](/docs/en/settings-reference#what-runs-under-allowmanagedhooksonl…admin-setup 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
What condition BJ() actually represents and what practical effect it has beyond the existing allowManagedHooksOnly policy is not stated.
Anthropic's documentation agrees
Anthropic's documentation has since written up allowManagedHooksOnly, on Set up Claude Code for your organization.