After Claude Code 2.1.325, a scheduled frontend build, UI check or refactoring job may pause for a permission decision. The practical task is to distinguish completed, waiting, failed and deliberately stopped work.
The compatibility condition
Anthropic's changelog describes a behavior change for sandboxed Bash and permission gates for scheduled tasks and /loop workflows that invoke skills, allowed tools or hooks. It does not establish that every workflow is broken.
Run a bounded check
In a non-production repository, record the Claude Code version, task definition, sandbox mode and allowed-tool configuration. Run one direct command and one scheduled or /loop task, then record whether each completed, asked for approval or remained waiting.
Do not broaden permissions blindly
If an unattended workflow needs to continue, define the smallest explicit permission set and retain a human fallback for new tool requests. Do not use a broad allow rule merely to restore an earlier behavior.
Use handoff states
Completed means the reviewer checks output. Waiting means a named operator decides. Failed means the build owner investigates. Stopped means the client or agency owner decides the next route.
Limits
Availability and behavior can differ by Claude Code surface, account and permission configuration. No client incident is claimed.