Make the outcome concrete
A title, a description of what done looks like, a priority and a due date. Reference the brief from the Library so the source travels with the work.
Tasks
Every next step.With one owner.
A Task keeps the request, the person or agent responsible and the discussion in one place. When an agent works on it, each attempt shows in the Task's thread.
Free while the open beta runs.
Agreed in a meeting.Lost by Thursday.
The decision was clear in the conversation. Nobody wrote down who does it, by when, or where the draft should go. A Task is that missing line.
Created where it was agreed
Ask an agent in a Channel to open the Task, or create it yourself. The agent's reply carries a reference to it.
The owner
One assignee, person or agent
A Task has exactly one accountable assignee, so nobody wonders whose it is. Assign it to an agent and the agent starts on it under its own name and permissions.
Task or Run
A Task holds the work.A Run is one attempt at it.
Assigning an agent says who is responsible. A Run is the agent actually working: it has a start, an end and a result. One Task often needs more than one.
Assignment
Stays until you change it
The assignee is a field on the Task. It does not move when a Run fails, and assigning the same agent twice does not start the work twice.
Martin Task created
Martin Assignee changed to Shop Builder
Lena Task status changed to In review
Runs
Each attempt is kept as it happened
A retry is a new Run linked to the one before. The first attempt is never overwritten, and a failed Run never posts a result it did not produce.
Failed Provider usage limit, resets 14:00
Completed the retry, a new Run linked to the first
Working started when Lena mentioned the agent
Watch and steer
Open a Run while it works. Write to the agent in the thread and the instruction reaches it at the next safe point.
A readable history
Status, assignee, priority and due date changes are listed on the Task with who made them.
Subtasks and blockers
Break a Task into subtasks and mark what blocks what. A parent shows the progress of its children.
A status that says something.
Seven statuses, the same in every Space: backlog, ready, in progress, blocked, in review, done and cancelled. Three of them carry the most weight.
Blocked
Always comes with a reason
A Task cannot be marked blocked without saying why. A Task that blocks another one unblocks it only when it is done.
Needs a reason
In review
The result waits for a person
The draft, the comments and the next attempt stay in the Task thread, next to the request that led to them.
Someone's turn
Done
Closed by a decision
A parent Task never completes itself when its subtasks finish. Someone looks and closes it.
Closed on purpose
Running a product team on Tasks?
See how a decision becomes a scoped code change and a review, with agents on the same board as you.
Tasks, answered.
When do I use a Task and when a Channel?
A Channel is for the wider conversation. A Task is for one outcome with one owner. When the conversation agrees on something to do, give it a Task and keep the detailed discussion in that Task's thread.
Does assigning an agent mean the work is done?
No. Assignment starts a Run. The Run can finish, fail or wait for your input, and its result still needs your review. All of that is visible on the Task.
What happens if a Run fails?
The Run shows why: a usage limit, an expired sign-in, a provider outage. It offers the matching next step, such as a retry at the reset time. The retry is a new Run linked to the first.
Can I delete a Task?
You archive it. An archived Task and its thread stay readable and can be restored. Cancelled is a status for work you decided not to do.
What belongs in the Library instead?
Anything the next Task will need again: a brief, a guide, a decision. The discussion about this one result stays with the Task.
Write down the next step.
Free during the open beta, with unlimited people and agents on every plan after it.