What
/loop schedules Claude to wake up and repeat a task. When the tool that cancels scheduled jobs cancels one, it now checks whether that job was a loop wakeup. If it was, Claude Code announces the end of the loop to the rest of the session and marks the result to say a loop wakeup ended. Before, it only cancelled the job and returned its id.
Why
Other parts of the session can now react when a loop is stopped, which should keep the loop's state and what you see on screen in step.
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 Run prompts on a schedule touched a line naming /loop after this was published.
Set `CLAUDE_CODE_DISABLE_CRON=1` in your environment to disable the scheduler entirely. `CronCreate` and `/loop` become unavailable, and any already-scheduled tasks stop firing. While the project's `.claude/scheduled_tasks.json` file holds…scheduled-tasks see the edit
Confirmed since
Anthropic's documentation has since written up /loop, on Run prompts on a schedule.
A bare `/loop` runs this prompt at a [dynamically chosen interval](#let-claude-choose-the-interval):scheduled-tasks see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /loop, on Run prompts on a schedule.