Use Tasks to Track Work
Tasks turn agent work into something visible, reviewable, and resumable. Use them when work should not disappear inside a chat thread. If behavior changed after the task was created, Agent History helps an administrator check the assigned agent's configuration changes.
When To Create A Task
- A result needs review before it is sent or published.
- Someone needs to own follow-up work.
- The agent needs to continue work later with the same context.
- A workflow or tool result needs investigation.
- A conversation produced a concrete action item.
Statuses
The task board uses four operating states:
| Status | Meaning |
|---|---|
| Todo | Work is captured but not started. |
| In progress | The owner or agent is actively working. |
| In review | The output needs a human or teammate check. |
| Done | The work is complete and no more action is expected. |
Tasks can be reviewed in table or kanban style views. Use search and status filters when the list grows.
A Good Task Has
- A short outcome-focused title.
- The source conversation, file, or data collection.
- The assigned agent or owner.
- A clear expected output.
- Acceptance criteria or review notes.
Create a task for the Reporting agent. Goal: compare Q2 feedback themes with last quarter. Output: table of top issues, count, source examples, and recommended next action. Status: In review.
Recover Missing Context
If a task result looks detached from the original request, open the source conversation or task conversation history. If the source is missing, add it directly to the task before asking the agent to continue.