What is the task system?
A task is a unit of work that Agent can plan and execute. Each task runs in its own thread — a separate conversation where Agent works independently. You can follow along, give feedback, or let it run in the background. The task system is how Agent breaks work into manageable chunks. When you describe what you want to build, Agent splits your request into discrete tasks and organizes them on a board with columns: Drafts, Active, Ready, and Done.
How parallel tasks work
Plan your tasks
Start a conversation in the main thread, or create a new thread and plan there. Agent reviews your project, identifies what would have the most impact, and writes up a detailed plan for each task — including what it will do and what “done” looks like.

Review and accept
Agent proposes a set of tasks — each with a title, description, and a detailed plan you can inspect with View plan. Review the full list, then choose:
- Accept tasks — Start all tasks and send them to the background
- Revise plan — Ask Agent to adjust the tasks before starting

Tasks run in parallel
Once accepted, tasks run simultaneously — each in its own isolated copy of your project. Your main version stays untouched until you choose to apply changes. You can track progress in two ways:

- Thread view — Each task runs in its own thread with a live status indicator, so you can follow along or jump into any task’s conversation

- Board view — A column-based board showing all tasks organized by status: Drafts, Active, Ready, and Done

Review and apply
When a task finishes, Agent shows you what it did — the work log, test results, and a live preview of the changes. You decide what happens next:
- Apply changes to main version — Merge the task’s work into your project
- Dismiss — Discard the changes if they’re not what you wanted

Task states
Every task goes 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.
The task board
All your tasks live on a board organized into columns. Here’s how the board looks as tasks move through each stage.Drafts and Active
When you describe what you want to build, Agent creates draft tasks — each with a title, description, and a step-by-step plan. You can review the plan, ask Agent to adjust it, or accept it as-is. Once you accept, tasks move to the Active column and Agent starts building them. Each task runs in its own isolated copy of your project, so nothing changes in your main version until you say so. Some tasks depend on others — for example, a task that builds a dashboard needs the database to be set up first. These tasks wait as queued until their dependencies finish. Tasks also queue if you’ve reached your plan’s limit for parallel tasks.Ready and Done
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’re in control. You can apply changes in two ways:- From the thread — Open the task’s thread and you’ll see a review prompt like the one below. Press Apply changes to main version to bring the work into your project, or Dismiss to discard it.
- From the board — Click the three-dot menu on any Ready task card to see your options, then press Apply changes
What you can build
The task system works for any project. Here are a few patterns where it shines:- Ship faster with parallel tasks — Build authentication, a dashboard, and an API layer simultaneously instead of sequentially
- Plan complex projects — Break a large feature into well-scoped tasks with dependencies, then execute with confidence
- Explore design directions in parallel — Try multiple UI approaches at the same time and pick the best result
Frequently asked questions
Do I need to change how I build?
Do I need to change how I build?
No. The main thread works exactly the same. Agent automatically creates tasks behind the scenes when it helps. You can also use Plan mode to see and manage tasks explicitly.
Why are my tasks running one at a time?
Why are my tasks running one at a time?
Parallel execution supports up to 10 concurrent tasks on Pro and up to 2 on Core (for a limited time). If you’re hitting the limit, additional tasks queue and run as slots free up.
How does Agent handle conflicts when applying background tasks?
How does Agent handle conflicts when applying background tasks?
Agent uses AI-assisted conflict resolution. It understands what each task was trying to accomplish and applies the changes intelligently. If something looks off, you can ask Agent to fix it in the thread.
Can tasks depend on each other?
Can tasks depend on each other?
Yes. Agent automatically detects dependencies — for example, a task that builds a dashboard depends on the task that creates the database schema. Dependent tasks wait until their prerequisites complete.
Availability
| Capability | Core | Pro |
|---|---|---|
| Task planning | ✅ | ✅ |
| Background tasks | ✅ | ✅ |
| Parallel execution | Up to 2* | Up to 10 |