{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}
;
};
Every Agent task moves through a lifecycle: planned, running, ready for review, and finished. The lifecycle keeps work isolated until you decide what should become part of your main version.
## Draft
A **Draft** is a task Agent has planned but has not started building yet. Drafts are safe to review because they only contain the proposed work: the task title, description, and plan.
Use Drafts to decide whether Agent understood the goal. You can start the task, ask Agent to revise the plan, or archive the draft for later.
## Active
An **Active** task is running in the background. Agent works on it in an isolated copy of your project, so your main version stays unchanged while the task runs.
You can keep using the main thread while Active tasks run. If a task needs feedback, open its thread and continue the conversation there.
## Queued
A **Queued** task is approved but waiting to start. A task can queue when it depends on another task, or when you have reached your plan's active background task limit.
Queued tasks start automatically when their prerequisites finish and an active task slot opens.
## Ready
A **Ready** task is finished, but its changes have not been applied to your main version yet. Review the task's work log, test results, and preview before applying changes.
If the work looks right, apply it to main. If it is not what you wanted, dismiss it and start a new task.
## Applying
An **Applying** task is in the middle of moving its changes into your main version. Agent handles conflicts automatically when applying changes from multiple tasks.
Wait for applying to finish before judging the final result. If something looks off afterward, ask Agent to fix it in the main thread.
## Done
A **Done** task is finished and no longer needs action. Done can mean the task was applied to your main version, archived before it started, or cancelled after it moved into building.
Use the **Done** column as a history of completed, archived, and cancelled task work.
## State examples
Every task moves through a series of stages, from an idea to part of your app. Each stage has its own icon so you can tell what's happening at a glance.
Draft: Agent has proposed this task. It has a plan ready for your review.
Active: Agent is building this task right now. It runs in its own copy of your project so your main version stays safe.
Queued: This task is approved but waiting for a slot to open up before it can start building.
Ready: This task is complete. You can review the changes and apply them to your main version whenever you're ready.
Applying: The changes from this task are being applied to your main version right now.
Done: This task is finished and its changes are part of your main version.
Archived: A planning session you set aside before it started building. Archived planning sessions can be restored later from the Done column.
Cancelled: A task you stopped after it had moved into building. Cancelled tasks can't be restored. Start a new task if you change your mind.
## Archiving and cancelling tasks
You can stop a task at any point in its lifecycle, but the option you see depends on where the task is on the board. Both **Archive** and **Cancel** move a task to the **Done** column, but they behave differently:
| Action | When it's available | What happens | Reversible? |
| ----------- | --------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| **Archive** | While the task is still a planning session: a **Draft** that hasn't started building | The planning session is set aside without running. Its plan is preserved. | Yes. Open the archived card in the **Done** column and restore it back to **Drafts**. |
| **Cancel** | After the task has moved from planning into building: any **Active**, **Queued**, or **Ready** task | Agent stops the task and discards any in-progress work. No changes are applied to your main version. | No. Cancelled tasks can't be restored. Start a new task if you want to revisit the work. |
Use **Archive** for planning sessions you want to revisit later. Use **Cancel** as the permanent stop button for tasks that are queued, already running, or finished building.
You can find both archived planning sessions and cancelled tasks in the **Done** column on the far right of the task board, alongside completed tasks.
## Draft
A **Draft** is a task Agent has planned but has not started building yet. Drafts are safe to review because they only contain the proposed work: the task title, description, and plan.
Use Drafts to decide whether Agent understood the goal. You can start the task, ask Agent to revise the plan, or archive the draft for later.
## Active
An **Active** task is running in the background. Agent works on it in an isolated copy of your project, so your main version stays unchanged while the task runs.
You can keep using the main thread while Active tasks run. If a task needs feedback, open its thread and continue the conversation there.
## Queued
A **Queued** task is approved but waiting to start. A task can queue when it depends on another task, or when you have reached your plan's active background task limit.
Queued tasks start automatically when their prerequisites finish and an active task slot opens.
## Ready
A **Ready** task is finished, but its changes have not been applied to your main version yet. Review the task's work log, test results, and preview before applying changes.
If the work looks right, apply it to main. If it is not what you wanted, dismiss it and start a new task.
## Applying
An **Applying** task is in the middle of moving its changes into your main version. Agent handles conflicts automatically when applying changes from multiple tasks.
Wait for applying to finish before judging the final result. If something looks off afterward, ask Agent to fix it in the main thread.
## Done
A **Done** task is finished and no longer needs action. Done can mean the task was applied to your main version, archived before it started, or cancelled after it moved into building.
Use the **Done** column as a history of completed, archived, and cancelled task work.
## State examples
Every task moves through a series of stages, from an idea to part of your app. Each stage has its own icon so you can tell what's happening at a glance.