What
An organisation can use managed settings, which are settings controlled by an administrator, to set allowManagedPermissionRulesOnly. When that is set, only the administrator's permission rules count. Permission rules decide which tools Claude Code may use without asking. With this setting on, the status panel now shows a "Permission rules" row. The row lists any allowed tools that were ignored in this session.
Why
If you allowed tools yourself, for example with --allowedTools, and they had no effect, this row tells you why.
Names in the bundle/statusallowManagedPermissionRulesOnly
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 allowManagedPermissionRulesOnly, on Set up Claude Code for your organization.
| [Permission lockdown](/docs/en/permissions#managed-only-settings) | Make managed settings the [only settings source of permission rules](/docs/en/settings-reference#allowmanagedpermissionrulesonly). Disable `--dangerously-skip-permission…admin-setup see the edit
Added since
A small documentation edit on How Claude remembers your project touched a line naming /status after this was published.
If one of your instruction files is over the recommended length, you see a warning at startup and when you run `/status`. You also see a warning when files that are each within that length add up past a combined limit at session start. Eac…memory see the edit
Confirmed since
Anthropic's documentation has since written up /status, on Configure server-managed settings.
The startup notice, `/status`, and `claude doctor` then report the [failed load](/docs/en/errors#remote-managed-settings-failed-to-load) with the cause `no setting in the server response could be applied as written`, and that entry says wh…server-managed-settings 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 confirmed that this panel is the one opened by `/status`.
Anthropic's documentation agrees
Anthropic's documentation has since written up /status, on Configure server-managed settings.
Anthropic's release notes agree
Added a startup notice, and /status and claude doctor entries, listing telemetry variables in a project's settings files that were ignored…