Yesterday I wrote about Claude Desktop v5.11492 and auto mode starting its own sessions. The same day, v5.11492.5 followed, and it has a change you’ll notice if you use Claude Code in the desktop app. It bundles Claude Code 2.1.325, which among other things fixes a security issue in how zstd-compressed responses are decoded.
Sandboxed shell commands ask first
Until now, most shell commands in the sandbox on macOS and Linux ran without a prompt. Now most of them ask first when you’re in Manual or Accept edits mode, and auto mode checks many of them. The changelog is upfront about the consequence: a routine can stop at one of these prompts.
To get the old behavior back, add "autoAllowBashIfSandboxed": true to the sandbox block of ~/.claude/settings.json, creating the file if it doesn’t exist.
Two more changes point the same way:
git worktree add,moveandremovefail inside the sandbox, as does a commit in a worktree the session wasn’t started in or given.- Shell allow rules that name a variable, such as
Bash(NODE_ENV*), stop matching. Those commands now ask for approval.
There’s also a practical addition: workflows in local sessions now pause when you hit your plan’s usage limit and pick up after the reset, as long as the reset is within a day and “Auto-continue when limits reset” is on.
For admins: the same switch, plus stricter certificates
The third-party platform section repeats the sandbox change, since the sandbox is on by default on managed macOS and Linux machines. Admins set "autoAllowBashIfSandboxed": true in managed-settings.json (for SSH, on the host). A newly created file also needs a top-level "parentSettingsBehavior": "merge".
Certificate checks got stricter too. Under a company CA that limits DNS names, a certificate with IP addresses but no DNS name is refused if its common name is an IP address or a domain the CA doesn’t allow. Requests to such a gateway fail until its certificate lists an allowed DNS name.
If routines run overnight, check them today
More prompts in the sandbox make sense from a security angle, especially in a week when auto mode was handed more power. For unattended work it’s a trap: a routine that ran clean yesterday may now sit waiting for an approval nobody gives. If you use scheduled tasks, watch the next few runs and decide on purpose whether that one line in settings.json is worth the risk.