Scheduled tasks
Run an agent task automatically — on a cron, a fixed interval, or once at a future time — and review every run.
The work that drains a small team is the work that repeats: the Monday report, the hourly inbox sweep, the nightly backup. Scheduled tasks let an agent do all of it on its own — you define the task once, set when it runs, and review the results when you're ready.
Create a scheduled task
Open Automations
Go to Space settings → Automations, then click New scheduled task. (Your plan sets how many scheduled tasks you can have, the shortest allowed interval, and whether cron is available.)
Define the task template
Give the task a name and (optionally) a description, then write the prompt the agent should run each time — the same plain-language brief you'd type into a task. You can also set the model and reasoning effort, choose a project, and decide whether each run starts a new session or reuses an existing one.
Pick a schedule
Choose one of three schedule types:
- Cron — a cron expression for precise recurring runs (e.g. every weekday at 9 AM), with a timezone.
- Interval — a fixed number of minutes between runs.
- Once — a single run at a future date and time.
Optionally cap the total number of runs with a max runs limit.
Save and let it run
Save the task. It runs automatically on schedule, and Buda shows the next run time. Each run dispatches to the agent just like a manual task.
Enable, disable, and run now
- Enable / disable — toggle a task on or off without deleting it. Disabled tasks keep their template and history.
- Run now — trigger a run immediately to test a task or get an off-schedule result; this doesn't change the schedule.
- Edit / delete — update the template or schedule any time, or remove the task entirely.
Review run history
Open a task's history to see every run: when it started and completed, and its status — Pending, Running, Completed, Failed, or Skipped. Failed runs show the error, and each run links to the session it created so you can open the full output.
Scheduled tasks and Skills work well together: package an SOP as a skill, then schedule a task that runs it on a cadence.