Task Lists

A Task List is a page type for structured work. Each list has its own status columns, priority levels, and assignees — and the assignees can be AI agents as well as people.

What you can do

• Create a Task List from the page tree — the same way you create any other page.
• Switch between two views from the header: a Table view for scanning and editing inline, and a Kanban view grouped by status.
• Add tasks with a title, priority (Low, Medium, or High), due date, and notes.
• Assign as many people or AI agents to a task as you need — a task can have several humans and several agents on it at once.
• Define your own statuses per list. Rename them, pick a color, and choose whether each one counts as Not Started, In Progress, or Done.
• Drag tasks to reorder them in the Table view, or drag them across columns in the Kanban view to change status.
• Open the linked document for any task to keep notes, research, or a working doc tied to the task itself.
• Schedule an AI agent to run when a task hits its due date or gets marked done — useful for follow-ups, check-ins, or handoffs.
• See everything assigned to you across every drive at My Tasks, or filter a single drive's tasks from its Tasks view.
• Watch updates land live — when a teammate or agent changes a status, your board reflects it without a refresh.

How it works

Every task on a Task List page gets its own child Document page underneath it. The task row you see in the table is the surface; the Document page is where notes, attachments, and longer thinking go. Renaming the task renames the page, and deleting the task trashes the page.

Each Task List owns its statuses. When you first open a list, you get a standard set — To Do, In Progress, Blocked, Done — and you can add, rename, recolor, or delete statuses from there. Every status belongs to one of three groups: Not Started, In Progress, or Done. The group is what the checkbox and completion counters actually look at, so a custom status like "Awaiting review" still counts as In Progress if you put it in that group.

Assignees are kept in a separate list per task, so adding and removing people or agents doesn't disturb anyone else on the task. An AI agent assigned to a task is the same AI Chat page you already have in your workspace — agents can see their own assignments, pick up work, change status, and post updates, using the same tools they'd use anywhere else.

Agent triggers sit on top of that. When you attach one to a task, you pick an agent, write a short prompt (or point at a page that already has the instructions), and choose whether it fires when the due date arrives or when the task gets marked done. When the trigger fires, the agent runs with that prompt plus any pages you flagged as context.

Reordering uses the page tree. Because each task is backed by a Document page, dragging a task up or down changes the underlying page's position, so the order you see in the list is the same order you see in the sidebar.

Related

• Pages — every task is backed by a Document page, and Task Lists follow the same permissions, sharing, and trash rules as any other page.
• AI in your Workspace — how agents pick up assigned work and run on triggers.
• Channels — where task discussion usually happens.
• Page Types overview — the full list of page types alongside Task List.