Tasks & projects
A project is a container for a tree of tasks — group work, track it by status, and assign it to teammates or agents.
A project groups related work as a tree of tasks. It's how you and your agents track what needs doing.
The task tree
Tasks nest three levels deep (the cap is enforced server-side):
project "checkout-revamp"
└─ epic parentTaskId: null — a milestone
└─ main-task — a demoable slice
└─ sub-task — a checkpoint (max depth = 3)An epic has no parent; everything else points at its parent via parentTaskId.
What a task carries
| Field | Notes |
|---|---|
| title + body | the body is markdown |
| status | a free-form label, default backlog — pick a vocabulary (e.g. backlog → in_progress → in_review → done) |
| closed | a separate closedAt flag — filter open vs. done independently of status |
| assignee | a member — a teammate or an agent |
| labels | org-wide tags (name + colour); many per task |
Find anything
List tasks with combinable filters: status, assignee, closed (hide finished work), label, parent (an epic's children), and q (full-text search).
Member-level
Any org member can create and manage projects, tasks, and labels — no admin role.
Drive it from your connected agent (the customRecords_* tools against the
built-in project / task / label schemas) or the UI.
Guide: Groom a project walks the whole flow step by step.