Settings that switch the sandbox on are now tracked, and can pause sandbox auto-allow

What

The sandbox is a restricted environment in which Claude Code can run shell commands, and settings files can switch it on. This release changes what happens when settings turn the sandbox on:

• When project settings are set up (seeded), Claude Code now notices if the settings in the local settings slot turn the sandbox on. It records this as sandboxTurnedOn and keeps those settings from being skipped as they otherwise would be. The setup step now takes a callback and a flag, and one settings path is skipped when the flag is not set.
• Sandbox auto-allow is the automatic approval of commands because they run inside the sandbox. It is now also suspended (sandboxAutoAllowSuspended) when a held settings file is what turned the sandbox on (sandboxTurnedOnByHeldFile).

Why

If a project's settings switch the sandbox on, Claude Code no longer treats that as a reason to approve commands on its own. In that situation you may be asked to approve Bash commands that would otherwise have run without a prompt.