Claude Code Sandboxed Bash Commands Now Follow the Normal Permission Flow by Default

Claude CodeView original changelog

Claude Code 2.1.325 changes sandboxed Bash commands to go through the normal permission flow by default. To keep running them without prompts, users set sandbox.autoAllowBashIfSandboxed: true. Managed settings that turn the sandbox on now need the same setting in the highest-ranking managed source to keep commands prompt-free.

Key Takeaways

  • Sandboxed Bash commands now prompt by default like other commands.
  • The opt-out is sandbox.autoAllowBashIfSandboxed: true.
  • Managed setups need the setting in their highest-ranking managed source.
  • Users who relied on the sandbox to skip prompts may see new prompts after updating.
  • The change makes skipping the prompt an explicit choice.
  • It ships alongside several Bash permission fixes in the same release.

A default that flipped

Before 2.1.325, a Bash command that ran inside the sandbox could run without a permission prompt. Claude Code 2.1.325 changes this so sandboxed Bash commands follow the normal permission flow by default. A user who wants the old behavior sets sandbox.autoAllowBashIfSandboxed: true.

Managed settings

The same applies to managed settings that turn the sandbox on. To keep commands running without prompts, sandbox.autoAllowBashIfSandboxed: true must be set in the highest-ranking managed source. Teams that relied on the sandbox alone to approve commands may start seeing prompts after updating.

Why it matters

The change makes the permission prompt the default checkpoint again, and makes skipping it an explicit choice. It lands in a release that also patches several Bash permission gaps.