Skip to content
LongsurfLongsurfLongsurf Docs

Scheduled Tasks

Scheduled tasks let a user create one-time or recurring agent prompts. A schedule is durable product state, not a browser timer or an external Airflow DAG.

Contract

Section titled “Contract”
  • Postgres stores the current schedule definition and next due cursor.
  • Each accepted fire creates one ordinary scheduled session and run.
  • Occurrence history links logical fire times to root agent runs.
  • Dispatch is idempotent across retries, restarts, and API replicas.
  • Immediate, alert, and scheduled runs share the same execution cap owner.

Product Impact

Section titled “Product Impact”

Schedules can refresh semantic watchlist columns, run recurring research, produce notifications, or execute future workflow parts. The schedule owns when the task fires; the normal agent lifecycle owns the run.

Source docs: docs/vision/agent-scheduled-tasks.md and docs/vision/agent-lifecycle.md.