{"version":"2.1.71","anchor":"loop-command-scheduled-recurring-prompts","canonical_anchor":"loop-command-scheduled-recurring-prompts","heading":"\/loop Command (Scheduled Recurring Prompts)","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.71\/e\/loop-command-scheduled-recurring-prompts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.71","markdown":"### \/loop Command (Scheduled Recurring Prompts)\n\n**What**\n\nA new `\/loop` slash command that schedules prompts to run on a recurring interval, enabling automated monitoring, polling, and periodic tasks within a Claude Code session.\n\n**Usage**\n\n`\/loop 5m \/babysit-prs \/loop 30m check the deploy \/loop 1h \/standup 1 \/loop check the deploy (defaults to 10m interval)` **Details** - Supports intervals in seconds, minutes, hours, or days (e.g., `5m`, `30m`, `2h`, `1d`). Minimum granularity is 1 minute - Also supports standard 5-field cron expressions for precise scheduling (e.g., `\"*\/5 * * * *\"` for every 5 minutes, `\"30 14 * * 1-5\"` for weekdays at 2:30pm) - Jobs are session-only by default (die when Claude exits), but can be persisted to `.claude\/scheduled_tasks.json` to survive restarts - Recurring tasks auto-expire after 3 days - A small deterministic jitter is added to fire times to avoid thundering-herd effects - Only fires while the REPL is idle (not mid-query) - Uses file-based locking so only one Claude session runs the scheduler at a time - Three new internal tools: `CronCreate`, `CronDelete`, `CronList` **Evidence** Cron expression parser (search for `\"Standard 5-field cron expression\"`) \u2014 `_a6` at line ~449603. Loop command (search for `\"\/loop\"`)"}