Claude Code Scheduled Tasks and /loop Now Ask Before Running Skills With Allowed Tools or Hooks

Claude CodeView original changelog

Claude Code 2.1.325 makes scheduled tasks and /loop ask before running a skill that declares allowed-tools or hooks. Adding Skill(name) to the allow list runs it unattended. In Desktop, IDE and SDK hosts, "Always allow" now offers a rule alone only when saving it would allow that command again.

Key Takeaways

  • Scheduled tasks and /loop now ask before running skills with allowed-tools or hooks.
  • Skill(name) in the allow list lets such a skill run unattended.
  • "Always allow" now offers a rule alone only when it would allow the command again.
  • Some scheduled tasks that ran unattended may now wait for the user.
  • The change targets skills that can grant tools or run hooks.
  • It applies in Desktop, IDE and SDK hosts for the "Always allow" part.

Unattended runs now ask first

A scheduled task or /loop that invokes a skill declaring allowed-tools or hooks now asks before running it. To run such a skill unattended, add Skill(name) to the allow list.

"Always allow" in Desktop, IDE and SDK hosts

A rule alone is offered only when saving it would allow that command again. A scheduled task that relied on an "Always allow" rule that did not actually cover the command can now wait for the user.