{status === "done" ? : status === "draft-static" ? : status === "draft-done" ? : status === "active-queued" ? : status === "ready-drop" ? : }
{title}
{showMenu &&
Apply changes
Cancel
}
{}
{description &&
{description}
}
{}
{statusLabels[status] || status} • {timestamp}
;
};
## How the task board works
The task board gives you one place to review, start, monitor, and apply Agent tasks. Use it when Agent breaks a large request into multiple pieces, when you want to run work in the background, or when you need to understand what has already changed in your project.
Tasks are organized into columns based on status. The board shows what Agent has planned, what is running, what is ready for review, and what has already been applied.
Each task moves from left to right as it progresses:
* **Drafts**: tasks Agent has planned but has not started
* **Active**: tasks Agent is building now, including tasks queued behind your active task limit
* **Ready**: tasks Agent has finished and are ready for your review
* **Done**: tasks that are finished, archived, or cancelled
## Drafts
**Drafts** are planned tasks that Agent has not started building yet. Each draft includes a title, description, and step-by-step plan.
Use Drafts to review Agent's proposed approach before work starts. You can inspect the plan, ask Agent to adjust it, or start the task when you're ready.
Drafts are useful when you want to plan a larger feature before committing background work. For example, Agent might split an onboarding project into separate drafts for authentication, profile setup, dashboard UI, and deployment polish.
## Active
Once you accept a task, it moves to the **Active** column and Agent starts building. Each task runs in its own isolated copy of your project, so nothing changes in your main version until you apply the work.
Some tasks depend on others. For example, a task that builds a dashboard may need the database schema task to finish first. Dependent tasks wait as **Queued** until their prerequisites finish. Tasks also queue if you reach your plan's active background task limit.
## Ready
When a task finishes building, it moves to **Ready**. This means the work is complete, but nothing has changed in your main version yet.
You can apply changes in two ways:
* **From the thread**: open the task's thread and select **Apply changes to main version** to bring the work into your project, or **Dismiss** to discard it
* **From the board**: select the three-dot menu on any Ready task card, then select **Apply changes**
Review Ready tasks before applying them. Check the work log, test output, and preview so you understand what Agent changed.
## Done
Once applied, the task card moves to the **Done** column.
The Done column also includes archived planning sessions and cancelled tasks. This gives you a history of what happened without mixing finished work back into Drafts or Active.
Agent handles conflicts automatically when you apply changes from multiple tasks. If something doesn't look right, ask Agent to fix it.
## Find and filter tasks
Use the task board when your project has many tasks in flight. You can search by task title or task number, filter drafts, and use edit mode to manage groups of tasks at once.
For example, search by task number when someone references a task from a thread, review, or Slack conversation. Filter drafts when you want to focus on planned work without scanning active or finished tasks.
For suggested follow-ups, see [Follow-up tasks](/references/agent/follow-up-tasks).
## Rename a task
Long-running task lists can get hard to scan as scope shifts. To rename any task, open the three-dot menu on its card (in the task list sidebar or on the task board) and select **Rename**. Type a clearer title and select **Save**.
Renaming a task only changes how it appears to you and your teammates. The work Agent has already done, the task's history, and any pending changes are untouched.
## Settings on each task
Every task has its own settings dropdown next to its title. Open it to control how Agent finishes the task and how the result lands in your project:
* **Auto-apply changes** (Drafts and Active): when the task is ready, apply it to the main version immediately instead of waiting for review.
* **Auto-approve plan** (Drafts): when Agent suggests a plan for the task, accept it automatically and start building.
* **Apply changes** (Ready): apply the finished work to your main version.
* **Rename**: change the title shown on the card.
* **Review changes** (Ready): jump straight to the diff for a task that's ready.
* **Cancel**: stop the task or remove a draft.
Auto-apply and auto-approve are quick actions you select once, not toggles you leave on. The menu keeps a consistent width so the labels don't shift as you open different tasks.
Tasks are organized into columns based on status. The board shows what Agent has planned, what is running, what is ready for review, and what has already been applied.
Each task moves from left to right as it progresses:
* **Drafts**: tasks Agent has planned but has not started
* **Active**: tasks Agent is building now, including tasks queued behind your active task limit
* **Ready**: tasks Agent has finished and are ready for your review
* **Done**: tasks that are finished, archived, or cancelled
## Drafts
**Drafts** are planned tasks that Agent has not started building yet. Each draft includes a title, description, and step-by-step plan.
Use Drafts to review Agent's proposed approach before work starts. You can inspect the plan, ask Agent to adjust it, or start the task when you're ready.
Drafts are useful when you want to plan a larger feature before committing background work. For example, Agent might split an onboarding project into separate drafts for authentication, profile setup, dashboard UI, and deployment polish.
## Active
Once you accept a task, it moves to the **Active** column and Agent starts building. Each task runs in its own isolated copy of your project, so nothing changes in your main version until you apply the work.
Some tasks depend on others. For example, a task that builds a dashboard may need the database schema task to finish first. Dependent tasks wait as **Queued** until their prerequisites finish. Tasks also queue if you reach your plan's active background task limit.
