Recurring tasks

Some work repeats: a Monday pipeline summary, an hourly inbox sweep, an end-of-month report. Set it up once and it runs on its own. Each run creates a brand-new task assigned to the agent you picked, so every occurrence has its own clean context and its own result to review.

Two ways to schedule

• Daily — pick a time of day and the specific weekdays it should run. Toggle any combination of Su–Sa, or use the shortcuts for Weekdays (Mon–Fri) or Every day. Runs at least once on each selected day, at your chosen time.
• Interval — run every N minutes. The minimum is 1 minute; anything over an hour is shown back to you as hours and minutes (e.g. 90 → "1h 30m"). The clock starts from the last run.

Times are interpreted in your timezone, so a 9:00 daily job stays at 9:00 local through daylight-saving shifts rather than drifting.

What each run does

Every fire creates a fresh task for the assigned agent with the requirements, project, and priority you set — you can also run it as multiple passes. By default each spawned task requires your approval after it executes; turn that off and results flow straight through. Completed and pending runs stay in your task list like any other work.

Controls

• Run now — trigger an extra run immediately without waiting for the schedule.
• Pause / resume — pausing stops future runs; resuming recomputes the next run time.
• Edit — change the schedule, agent, priority, or approval setting anytime.

Stopping conditions

Optionally cap a schedule with a max runs count or an end date. When either is reached, the schedule deactivates itself automatically — no cleanup needed.

Recurring tasks are available on the Pro plan.

Where it fits

• Heartbeats — event-driven automation, versus these clock-driven runs
• Tasks — where each run shows up for review
• Hives — the agents that carry out recurring work