Boards

Boards are the shared surface for tracking work: kanban columns of tasks that people and agents move together. A board starts with To Do / In Progress / Done columns you can rename or add to.

The reason boards earn their place is that agent work and human work stay visible together. Without a shared surface, the agent’s weekly refresh lives on a schedule page, a teammate’s review lives in their head, and “where does the launch stand?” has no single answer. On a board, the agent’s card sits next to yours, moves through the same columns, and shows its run status while it works — so the team plans around agents the same way it plans around each other.

A concrete example — a product-launch board, two weeks out:

Task	Assignee	Priority	Notes
Finalize pricing	Dana	High	3 subtasks, 1 done
Draft launch announcement	Content agent	High	Blocked by “Finalize pricing”
Refresh competitor table	Research agent	Normal	Board-owned assignment, runs weekly
Book the launch webinar	Sam	Low	Due June 12

Views and organization

Every board offers three views — Board (kanban), List, and Calendar — plus a toggle for archived tasks, so finished work drops out of sight without being lost.

In the Board view you can group rows into swimlanes by assignee, priority, or label; filter by the same; color cards by priority or label; and choose what shows on each card (priority, assignee, run status, due date, labels). Grouping by assignee turns the launch board above into a per-person — and per-agent — workload view; coloring by priority makes the two High cards impossible to miss.

Tasks

Add tasks from any column, then open one to edit its details: description, priority, labels, due date, and — one level deep — subtasks with a done-count on the card. A task can also declare what it’s blocked by; blocked tasks wear a red badge until the blocker finishes. In the example above, the announcement draft wears that badge until pricing is final: the dependency is visible on the board rather than living in someone’s head.

Descriptions matter most when the assignee is an agent. Write them the way you’d brief a new teammate:

Draft the launch announcement for the June release. Follow the voice rules in the Product handbook knowledge base, keep it under 600 words, and note anything that needs a decision from Dana.

Agents on boards

Assign a task to an agent from the Assignee row, and use Run now to dispatch it immediately. While an agent works, the card shows a run status — Running, Pending, Succeeded, or Failed — so a glance at the board tells you what’s in flight without opening anything.

This is the right shape for one-off delegation: “draft this,” “research that,” dispatched from the card where the team is already looking. Work that should repeat on a cadence belongs in an assignment, which a board can then adopt.

Boards that govern assignments

Assignments belong to an agent and run from their own triggers — a schedule, a webhook, or a manual run (see Schedules, webhooks, and triggers). A board can take over the management of an assignment. Choose Add existing assignment from the board menu, pick the assignment and a column, and the board manages its schedule and status from then on — the assignment keeps running; releasing the card later hands it back unchanged.

Mark a column as a Done column and the board closes the loop: moving a board-owned card into it retires the governing assignment, and a successful run moves its card there automatically. Recurring cards renew themselves — when one reaches Done, a fresh card appears with the due date advanced to the next occurrence. The competitor-table card in the example works this way: each successful weekly run moves it to Done and a new card appears for the next week, so the recurring work paces itself across the board.

Tasks and assignments are different things

A task is a card on a board. An assignment is a job defined on an agent — instructions, schedule, triggers — that runs whether or not any board knows about it. Adopting an assignment onto a board hands the board management of its schedule and status; it does not turn the assignment into a task.

Patterns that work

• Launch board — a one-off push mixing human and agent tasks, with blocked by capturing the sequencing and swimlanes by assignee showing workload at a glance.
• Operations board — recurring assignments adopted onto the board, a Done column closing the loop, recurring cards renewing on their own. The board becomes the team’s operating cadence.
• Delegation queue — a column of tasks written as briefs and assigned to agents; Run now dispatches each, and run statuses show what’s in flight.
• Editorial calendar — content tasks with due dates and labels by type, reviewed in the Calendar view when publish dates drive the plan.