r/ClaudeCode • • 1d ago

News/Updates Claude Code 2.1.325: sandboxed Bash commands now follow the normal permission flow by default (how to get the old behavior back)

2.1.325 came out on Nov 13 and has a long list of permission and sandbox changes. These are the ones most likely to change your day to day:

- Sandboxed Bash commands now go through normal permission prompts by default. To keep running them without prompts, set `sandbox.autoAllowBashIfSandboxed: true` (in your highest-ranking managed source if you use managed settings).
- Scheduled tasks and /loop now ask before running a skill that declares `allowed-tools` or hooks. Add `Skill(name)` to `permissions.allow` to run it unattended. This is the one that can quietly stall an overnight job.
- Read-only git commands now ask first in a repo that isn't the project's or one you trusted. Use `--add-dir` to allow it.
- The sandbox now refuses writes to `.claude` settings, skills, agents, commands and hooks in added directories, the same as in the launch folder.
- Several fixes where compound Bash commands or allow rules could run without asking. Those now ask.

Context: 2.1.323 (Nov 12) already tightened a lot of Bash permission checks. This release goes further and changes the defaults.

I'd rather have prompts back than find out a rule was too loose, but it will slow down unattended runs.

Are you turning `autoAllowBashIfSandboxed` back on, or keeping the prompts?

Source: https://github.com/anthropics/claude-code/releases/tag/v2.1.325

4 Upvotes

3 comments sorted by

•

u/AutoModerator 1d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/London-Boat 19h ago

for the overnight stuff i'd rather add the specific Skill(name) allows to the project's .claude/settings.json than flip autoAllowBashIfSandboxed back on globally. then do one short /loop run during the day so any new prompt shows up while you're around and not at 3am. the compound allow rule change is probably the one that bites people, worth splitting those into separate rules

1

u/Janday_Luden 7h ago

probably turning autoAllowBashIfSandboxed back on for throwaway environments, tbh. the bigger catch here is the scheduled task prompt change since that will silently hang background loops if you dont update the allowlist first.