Claude Code tightens sandbox defaults: sandboxed Bash now asks first, and admins must opt back in
Synopsis
Anthropic's Claude Code changelog says sandboxed Bash commands now follow the normal permission flow instead of running without a prompt just because they are sandboxed; restoring prompt-free execution requires setting sandbox.autoAllowBashIfSandboxed in the highest-ranking managed source. The same update stops the sandbox from writing to several sensitive home folders by default on macOS, Linux and WSL, and adds permissions.blockWritesOutsideWorkingDirectories so Write, Edit and NotebookEdit refuse paths outside the working directories in every permission mode. These changes move the default boundary for command execution and file writes; the changelog reports no effectiveness evaluation.
Interpretation
Sandboxing no longer implies approval: a Bash command wrapped in the sandbox now goes through the same permission flow as an ordinary command and runs only after the user confirms. Previously a sandboxed Bash command could run without a prompt, with the sandbox itself treated as a sufficient boundary. The changelog lists this as a default-behavior change and gives the switch that restores the old behavior, sandbox.autoAllowBashIfSandboxed: true, so both behaviors are selectable in the same version.
Prompt-free execution now has to be declared explicitly by an administrator in managed settings, rather than switched on incidentally by project or user settings. Previously the managed setting that turned the sandbox on was itself enough to let commands run without prompts. The changelog requires sandbox.autoAllowBashIfSandboxed: true in the highest-ranking managed source for commands to keep running without prompts when managed settings enable the sandbox.
The file-write boundary tightens at the same time: the new permissions.blockWritesOutsideWorkingDirectories makes Write, Edit and NotebookEdit refuse paths outside the working directories in every permission mode. The changelog lists this as a new setting and states that it applies in every permission mode, not only in one of them. The changelog states the setting covers every permission mode and groups it with the sandbox no longer writing to sensitive home folders by default, which sandbox.filesystem.allowWrite can reopen entry by entry.
Perspective
This report covers only the default permission behavior and configuration switches described in the Claude Code changelog, for developers and administrators who use or manage Claude Code; the changelog gives no measurement of how these defaults perform on real tasks.
The changelog notes that if every edit asks, any link in that folder pointing to an unreadable or network path should be removed; when managed settings enable the sandbox, the switch must be set in the highest-ranking source to keep commands prompt-free, otherwise each command asks.
