Autopilot

What It Does

Think of it as a project manager that runs in the background: it respects task dependencies, schedules work across multiple sessions, and keeps your business plan progressing while you focus on high-level decisions.

How It Works

1. 1
   Pick a task — the work queue selects the highest-priority task whose dependencies are all satisfied.
2. 2
   Assign the agent — the task's assigned team member (or the best-fit agent) opens a session and begins work.
3. 3
   Execute — the agent works through the task, producing deliverables and updating the business plan.
4. 4
   Move to Review — completed work is moved to the Review column. If the agent needs your input, it asks via the AskUserQuestion tool.
5. 5
   Next task — the pipeline picks up the next ready task and repeats.

Dependency-Aware Work Queue

Autopilot uses the task dependency graph to determine execution order. A task is only picked up when all of its prerequisites are in the Done column.

Multi-Session Pipelines

Autopilot can manage multiple sessions concurrently. Each task runs in its own session, and sessions are automatically linked to the task they serve. This means:

• Agents have full context from the task description and acceptance criteria
• Deliverables produced in the session are attached to the task
• You can review any session to see exactly what the agent did

Autopilot Controls

The Autopilot UI provides visual controls in the Project Workspace toolbar:

Scheduler Integration

Autopilot can be triggered by the built-in scheduler using cron expressions. For example, you could schedule a daily run at 9 AM to process overnight backlog. Configure schedules in your workspace config file.

Related