{"version":"2.1.246","anchor":"disabled-settings-files-no-longer-feed-rules-into-the-sandbo","canonical_anchor":"disabled-settings-files-no-longer-feed-rules-into-the-sandbo","heading":"Disabled settings files no longer feed rules into the sandbox","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/disabled-settings-files-no-longer-feed-rules-into-the-sandbo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Disabled settings files no longer feed rules into the sandbox\n\nRules from settings files you disabled no longer sneak into the sandbox policy.\n\n**What**\n\nWhen building the sandbox policy, Claude Code now checks whether each settings source is enabled. Permission rules and `sandbox.filesystem` entries from a disabled source are skipped and logged; disabled project and local sources also have their `sandbox.credentials` entries dropped. Previously those entries were applied anyway.\n\n**Details**\n\n- Applies on every sandbox policy build, with no flag to restore the old behaviour.\n- The skip is recorded at info level, naming the disabled source.\n\n**Evidence**\n\n`Sandbox: ignoring permission rules and sandbox.filesystem entries from disabled setting source `\n\n- Area: Sandbox\n- Names: `sandbox.filesystem`, `sandbox.credentials`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}