Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.257 ·

allowManagedPermissionRulesOnly semantics clarified/expanded

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

Under the hood Internal Changes
JSON All of v2.1.257
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.257,
Internal ChangesSection of the release

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
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