Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial

The allowManagedPermissionRulesOnly description now spells out exactly which rule sources it ignores and which still apply.

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaPermissionswhat it touches
KindInternal Changesin v2.1.257,
Under the hood

The allowManagedPermissionRulesOnly description now spells out exactly which rule sources it ignores and which still apply.

The description of allowManagedPermissionRulesOnly has been rewritten for precision: it now explicitly ignores permission rules from user, project, local, and --settings files, as well as allow rules from --allowedTools, while --disallowedTools and other deny/ask rules from the CLI or session still apply.

Read from
Names in the bundleallowManagedPermissionRulesOnly
Since it was published

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 Hooks reference. The `permission_suggestions` array isn't an exact list of the options you see, because each permission dialog builds its own options. Some dialogs, such as the one for file edits, don't read the array at all and derive their options from t… hooks see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up allowManagedPermissionRulesOnly, on Hooks reference.
Anthropic's release notes agreeFixed --disallowedTools and session deny rules being dropped after the first settings reload when allowManagedPermissionRulesOnly is enabled

See this entry in the whole of v2.1.257 →

Feedback