What
The tip that nudges you toward the /loop command (which runs any prompt on a recurring schedule, useful for monitoring deploys, babysitting PRs, or polling status) now runs its eligibility checks through renamed internal functions. The tip's text and the /loop command itself are unchanged.
Why
This is an internal rename with no described effect on behavior; it doesn't change what /loop does or when the tip appears.
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 Code in Claude Desktop on 3P touched a line naming /loop after this was published.
| `scheduledTasksEnabled` | When `false`, the routines list in Code is hidden and Code sessions start without Claude Code's in-session scheduling tools, so the `/loop` command cannot schedule recurring work. Cowork's scheduled tasks are tu…third-party/claude-desktop/code see the edit
Confirmed since
Anthropic's documentation has since written up /loop, on CLI reference.
| `--continue`, `-c` | Load the most recent conversation in the current directory, including a [background session that has finished](/docs/en/sessions#resume-a-session); opening finished background sessions requires Claude Code v2.1.257 o…cli-reference 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 CLI reference.