schedule

1# /schedule — Task Scheduling
2 
3## Orientation
4 
5**Use when:** scheduling a recurring or one-off remote agent run (cron-style, outside the current session).
6**Don't use when:** repeating work within the current session (use /loop); continuous unattended campaigns (use /daemon).
7 
8## Default execution path (READ FIRST)
9 
10**`/schedule add` does NOT call `CronCreate` by default.** It shells out to
11`node scripts/local-schedule.js` which installs a native OS entry (Windows
12Task Scheduler or Unix cron). Only pass `--remote` to use Anthropic's routine
13system, and only after explicit user confirmation.
14 
15**Why:** `CronCreate` counts against the account-wide **15 routine runs / 24h**
16cap; every fire of the scheduled task counts. See
17[docs/ROUTINE-QUOTA.md](../../docs/ROUTINE-QUOTA.md).
18 
19### Default flow — `/schedule add "<expr>" "<command>"` (no `--remote`)
20Run:
21```bash
22node scripts/local-schedule.js add "<expr>" "<command>" --confirm
23```
24Before running, show the cadence, project, prompt and persistence and obtain
25approval to create the OS task. Normal Claude permissions remain enabled. Do not
26add a bypass flag to make unattended execution succeed.
27 
28Then report the returned ID and the removal command. This survives session
29end, machine reboot, and consumes zero routine quota. Use
30`/schedule list` and `/schedule remove {id}` (which also shell out to
31`local-schedule.js`) by default. Remove tasks before uninstalling. New jobs require
32…