using-cronlisted

# Using Cron — Scheduled Prompts The harness gives you `CronCreate` / `CronList` / `CronDelete`. Use them when the user wants something to happen at a future time or on a recurring basis. Do NOT fall back to `Start-Sleep`, a todo entry, or "I'll remember to do this later" — none of those survive. ## Iron Law **If the user wants something to happen later, it goes in cron. Period.** A todo entry is not a reminder. A `Start-Sleep` blocks the session and dies with it. Cron is the only durable answer. ## Decision Tree ### One-shot vs recurring - **One-shot** (`recurring: false`): "remind me at 3pm", "in 30 minutes", "tomorrow morning check Y". Pin minute/hour/day-of-month/month to specific values. Fires once, then auto-deletes. - **Recurring** (`recurring: true`, default): "every hour", "weekdays 9am", "every 5 minutes". Standard cron wildcards. Auto-expires after 7 days — tell the user this. ### Session-only vs durable - **`durable: false`** (DEFAULT): job lives only in this Claude session, dies when the REPL exits. Use for "remind me in 30 min", "check the build in an hour", anything obviously this-session. - **`durable: true`**: persisted to `.claude/scheduled_tasks.json`, survives restarts. Use ONLY when the user says "permanently", "every day", "long-term", "keep doing this", or implies the job outlives the session. When in doubt: `durable: false`. Easier to re-create than to clean up stale durable jobs. ## Cron Syntax — 5 Fields, Local Time ``` minute hour day-o