Rules from settings files you disabled no longer sneak into the sandbox policy.
What's wrong with this entry?
When 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.
- Applies on every sandbox policy build, with no flag to restore the old behaviour.
- The skip is recorded at info level, naming the disabled source.
Sandbox: ignoring permission rules and sandbox.filesystem entries from disabled setting source
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
Sandbox filesystem.disabled description corrected on credential masks
Both mention sandbox filesystem credential
-
v2.1.224
Invalid sandbox credential settings now fail closed instead of being ignored
Both mention sandbox credential
-
v2.1.221
Sandbox proxy re-signs AWS SigV4 requests made with masked credentials
Both mention sandbox credential