# Automation overview

Automation is where your agents stop waiting for you. Put them on a schedule, queue work for them, and watch the runs — durable jobs that keep going even with the app closed.

## Three surfaces

Automation lives in the Workbench and is made of three connected views:

- Schedules — the triggers that start a run on their own: a cron cadence, an internal event, or an inbound webhook. See Schedules.
- Tasks — a queue of work you assign to an agent or crew, tracked from queued through to done.
- Queue & Runs — the operational view: what’s running now, what’s waiting, and the history of what already finished.

## Durable by design

A schedule isn’t tied to a window being open. The intent — “run this agent on this cadence” — is durable, so a job can fire and a run can keep going with the app closed. When you reopen Foxora, the queue and run history catch you up on what happened while you were away.

> Early-stage: authoring is real, execution is landingThe Automation authoring surface — creating schedules and tasks, choosing trigger types, toggling them on and off — is built and works today. The end-to-end executor that drives those triggers, and some of the live state shown in Queue & Runs, is still being wired up and is partly sample data for now. Treat schedules and runs as a preview of the model rather than a production scheduler, and don’t depend on a job firing unattended yet.