{"version":"2.1.286","anchor":"permission-context-for-served-calls-now-considers-deny-rules","canonical_anchor":"permission-context-for-served-calls-now-considers-deny-rules","heading":"Deny rules from settings now apply even when local rules are not honored","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/permission-context-for-served-calls-now-considers-deny-rules","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Deny rules from settings now apply even when local rules are not honored\n\nWhen Claude Code is not honoring local permission rules, it now still applies deny rules from settings and stops sandbox auto-allow\n\n**Unclear.** It is not clear which features or kinds of call run in the mode where local rules are not honored.\n\n**What**\n\nClaude Code decides whether an action is allowed by checking permission rules, which are entries in your settings that allow or deny particular actions. In some cases it runs in a mode where it does not honor locally set rules. Previously, in that mode it used no rules at all. Now it still collects deny rules from your settings sources.\n\nIn the same mode, sandbox auto-allow is now suspended. A sandbox is a restricted environment that limits what a command can reach, and auto-allow is the behaviour where commands inside it are approved without asking.\n\n**Why**\n\nDeny rules you have written are now respected in more situations. That includes calls that are served or run remotely, where previously they could have been skipped because the rule list was empty.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}