What
The tool that lets a long-running /loop schedule its own next wake-up used to refuse and log a gate_off event when a server-side switch was off. That check is gone, so the tool works for anyone who can call it, and it now only declines once the loop has hit its maximum duration.
Details
- The refusal text no longer mentions the switch; the remaining refusal cites max duration only and tells the model not to re-issue.
- No setting replaces the removed check.
Evidence
Wakeup not scheduled. The loop reached its maximum duration — the loop has ended; do not re-issue.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/loop
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Common workflows touched a line naming /loop after this was published.
| [`/loop`](/docs/en/scheduled-tasks) | The current CLI session | Quick polling while a session is open. `--resume` and `--continue` restore unexpired fixed-interval loops. |common-workflows see the edit
Confirmed since
Anthropic's documentation has since written up /loop, on Schedule recurring tasks in Claude Code Desktop.
| | [Cloud](/docs/en/routines) | [Desktop](/docs/en/desktop-scheduled-tasks) | [`/loop`](/docs/en/scheduled-tasks) |desktop-scheduled-tasks see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /loop, on Schedule recurring tasks in Claude Code Desktop.
Anthropic's release notes agree
Changed /loop: self-paced dynamic mode and the no-prompt autonomous default are now always available, including on Bedrock/Vertex/Foundry