# Tasks & runs

Tasks are the work you hand to an agent or crew; runs are what executing that work looks like. Together they're the queue and the history of everything your agents are doing.

## The task queue

Open Automation → Tasks to see work assigned to agents and crews, grouped by state. Click New task to add one. Each task has:

- Title & description — what needs to happen, and any acceptance criteria.
- Assignee — the agent or crew that owns it.
- State — Running, Queued, Blocked, or Done.
- Priority — Low, Normal, or High.
- When — free text like now, in 2h, or waiting on approval.

### Moving through states

Tasks flow from Queued to Running to Done, and can sit in Blocked when they’re waiting on something — an approval, a dependency, a person. High-priority tasks are flagged in the list so the important work stays visible.

## Queue & Runs

Open Automation → Queue & Runs for the operational view. It has two tabs:

- Active — what’s running now and what’s queued, with a live status dot per run.
- History — completed and failed runs, each with the agent, a one-line summary, and how long it took.

> Where runs come fromA run can start from a schedule firing, a task being picked up, or a crew you kick off by hand. Whatever the source, it lands in the same queue — one place to watch everything your agents are doing.

> Run state is partly sample data todayThe Tasks and Queue & Runs screens are real UI, but the executor that keeps their live state in sync is still landing — some of what you see is seeded sample data for now. The shapes (states, priorities, history) are final; treat the live numbers as illustrative until the executor is fully wired.