What changed
v2.1.323 → v2.1.325: sandboxed Bash no longer runs without prompts by default — it now follows the normal permission flow. Scheduled tasks and /loop now ask before running a skill that declares allowed-tools or hooks.
TL;DR
Claude Code v2.1.325 changes two automation defaults: sandboxed Bash requires a prompt unless autoAllowBashIfSandboxed: true is set, and scheduled / looped runs pause before skills with allowed-tools or hooks unless pre-approved.
Developer signal
Two config changes to audit before the next auto-update:
(1) Sandboxed Bash: If you run Claude Code with sandbox enabled and expected Bash to execute without prompts, add { "sandbox": { "autoAllowBashIfSandboxed": true } } to your highest-priority managed settings source (or project/user settings). Without it, any CI or unattended run that uses Bash will now pause and wait.
(2) Scheduled tasks / /loop skills: If a skill in your loop declares allowed-tools or hooks, add it to your allow list: { "permissions": { "allow": ["Skill(name)"] } }. Without this, recurring agent runs that call those skills will stall. The intent is that skills that can run code or call external tools require explicit authorization before running unattended.
Additional behavior changes to review: --add-dir (not additionalDirectories) is now the correct flag to allow git reads in added directories; claude remote-control now exits with status 4 on self-stop and 69 on registration failure (useful for service managers); CLAUDE_CODE_MAX_CONTEXT_TOKENS now also sets the context window for unrecognized claude-* model IDs (use alongside CLAUDE_CODE_DISABLE_1M_CONTEXT); marketplace ref now accepts any full commit ID on a branch or tag, but clients before v2.1.325 can't load such pins.