Tasks

A task is the smallest thing you delegate: one request, one deliverable. You describe what you want, an agent picks it up and runs it, and the result comes back for your review. Every task carries its own priority, timeline, execution log, and any files it produced.

What a task holds

• Priority — Low, Medium, High, or Critical, which affects the order agents pick work up.
• Assignment — the agent doing the work, and optionally the project it belongs to. A task can sit unassigned until an agent is matched to it, then run.
• Execution log — a step-by-step record of what the agent did, so you can see the reasoning and tool calls behind a result rather than just the final answer.
• Results — the deliverable, plus any previews (a working web app, document, PDF, image, or spreadsheet) and artifacts the agent generated.

Dependencies

Tasks can depend on other tasks. A task with prerequisites won't be picked up until every task it depends on is done — then it becomes eligible to run. This lets you queue a chain of work up front — research, then draft, then review — without babysitting each step.

Handoffs

An agent working a task can hand it off to another agent when the work needs a different skill. The handoff carries a reason and the context so far, and by default preserves the progress already made — so the receiving agent continues rather than starting over.

Statuses

You'll see a task move through these states:

• Pending — created, waiting to start.
• In Progress — an agent is actively working it.
• Review — the result is ready and waiting for your approval.
• Input — the agent needs an answer from you to continue.
• Blocked — waiting on a dependency.
• Paused — held for now.
• Done, Failed, or Cancelled — finished, errored, or stopped.

Higher-quality runs

A task can run in multiple passes — the agent produces a result, then reworks it across additional passes to refine quality before handing it to you.

Recurring tasks

Any task can be set to repeat on a schedule instead of running once. See Recurring tasks for daily, interval, and end-condition options.

Where it fits

• Projects group related tasks under a shared goal.
• Work is where new tasks come from your requests.
• Playbooks launch a coordinated set of tasks in one move.
• Memory carries context and learnings across tasks.