Routines

Recurring work backed by real routine runs

Routines should use Cloudflare Cron, queues, routine records, and visible run results. A routine is not complete just because a UI row exists.

Routine execution

A routine should record due, started, completed, failed, skipped, and blocked states. It should save output even when delivery is skipped.

Routine calendar

Entry route: /app/routines. Status: Partial. Data source: /api/agent/routines. Empty state: the routines intro screen appears before any calendar is shown. Populated state: real persisted routines render in a month calendar with a side list of scheduled tasks; routine cards open the real routine editor.

Heartbeat and watchdog

runtime-style heartbeat behavior is useful for detecting stalled work. In Taskcenter, watchdog decisions should be visible, scoped, and connected to the affected run.

Guardrails

Unattended routine runs should not self-replicate or create new autonomous schedules unless an authorized user explicitly approves it.