Claude Code 2.1.325 Makes Sandboxed Bash Ask; 2.1.326 Falls Back to Auto Mode When Org Policy Fails to Load

Claude Code logo(opens in new tab)Claude Code(opens in new tab)ImportantNovember 17, 2026Coding Tools
What happened
Claude Code 2.1.325 makes sandboxed Bash ask by default; 2.1.326 falls back to auto mode when org policy has not loaded and loads plugins with malformed manifests.
Why it matters
Unattended runs can stall at prompts, and managed fleets lose two safeguards admins may have relied on.
What to do
Set sandbox.autoAllowBashIfSandboxed deliberately, check deployed plugins, and decide whether self-hosted runners should use Anthropic's gh api.

Our verdict on Claude Code stays conditional, and these two releases are why. In four days, 2.1.325 (13 November 2026) and 2.1.326 (16 November 2026) moved permission defaults in both directions at once. If you run Claude Code in CI, on scheduled tasks, on self-hosted runners or across a managed fleet, pin your version and act on the changes below before the update reaches you.

What happened

2.1.325 (13 November): sandboxed Bash now asks

  • "Changed sandboxed Bash commands to follow the normal permission flow by default; set sandbox.autoAllowBashIfSandboxed: true to keep running them without prompts."
  • For managed settings that turn the sandbox on: "to keep commands running without prompts, set sandbox.autoAllowBashIfSandboxed: true in your highest-ranking managed source".
  • "Changed scheduled tasks and /loop to ask before running a skill that declares allowed-tools or hooks; add Skill(name) to permissions.allow to run it unattended."
  • pluginDigests "is deprecated and ignored".
  • "Fixed a security issue in how zstd-compressed responses are decoded." The changelog names no CVE or advisory.

2.1.326 (16 November): three loosened defaults

  • "Changed terminal and VS Code sessions with no mode set to start in auto mode, not Manual mode, when your organization's policy hasn't loaded."
  • "Changed enabled plugins that were refused for a malformed plugin.json display field: they now load, with their hooks and MCP servers; administrators should check the plugins they deploy."
  • "Self-hosted runner: Changed Linux and macOS sessions with no gh to get a built-in gh api by default, via Anthropic, which adds their GitHub sign-in, if any; --use-anthropic-gh false turns it off."

The same release also tightens two things: Claude's file tools now refuse writes to sign-in files such as .credentials.json, and sandboxed commands on macOS, Linux and WSL "no longer write to some sensitive home folders by default".

Why it matters

Unattended runs can stall. A job that counted on sandboxed commands, or on skills with allowed-tools or hooks, running without approval will now wait at a prompt nobody answers.

Managed fleets lose two safeguards. If your policy server is unreachable, sessions with no mode set now start in auto mode rather than Manual. Plugins that the malformed-manifest check used to block now load with their hooks and MCP servers.

GitHub calls can route through Anthropic. On self-hosted Linux and macOS runners without gh, the built-in gh api goes via Anthropic and carries the runner's GitHub sign-in, if any, unless you turn it off.

This fits a pattern we have covered since 2.1.287: each version moves permission defaults, so reading the changelog before every upgrade is not optional.

What changes for you

  • CI and scheduled jobs: decide deliberately whether to set sandbox.autoAllowBashIfSandboxed: true. For fleets, set it in your highest-ranking managed source.
  • Skills run by scheduled tasks or /loop: add Skill(name) to permissions.allow for each one that must run unattended.
  • Plugins: audit every plugin you deploy, since malformed-manifest plugins now load.
  • Self-hosted runners: pass --use-anthropic-gh false if GitHub calls should not route through Anthropic.
  • Managed policy: make sure it loads reliably, because 2.1.326 falls back to auto mode when it does not.
  • Version pinning: pin the version your CI uses and read each changelog before you move the pin.

What to do

  1. 1 For unattended or CI runs, decide whether to set sandbox.autoAllowBashIfSandboxed: true, in your highest-ranking managed source for fleets.
  2. 2 Add Skill(name) to permissions.allow for skills that scheduled tasks or /loop must run unattended.
  3. 3 Check every plugin you deploy now that malformed-manifest plugins load with their hooks and MCP servers.
  4. 4 On self-hosted runners without gh, pass --use-anthropic-gh false if GitHub calls should not route through Anthropic.
  5. 5 Make sure managed policy loads reliably, since 2.1.326 falls back to auto mode when it does not.

Affected tools & models

Never need to catch up again

The weekly delta: only verdict changes and act-now items. No digest filler.

By subscribing you agree to our Privacy Policy. Unsubscribe anytime.