Priority 10 is highest
Set priority from 1 to 10 on any task. The list re-sorts automatically so urgent work stays at the top—matching the task board rule that higher priority cards rise in the Waiting column.
A standing-task queue for every agent on your team—sorted by priority, filtered by agent, and one click away from Run. The same tasks appear on the task board and in agent chats, so nothing drifts out of sync.
To do is the control surface for work that should repeat or wait in queue—not one-off chat messages. Each row is a standing task on an agent, with priority, optional schedule, and actions your role allows.
Set priority from 1 to 10 on any task. The list re-sorts automatically so urgent work stays at the top—matching the task board rule that higher priority cards rise in the Waiting column.
Hit Run to launch the task text to that agent’s chat and start execution. If the agent is busy, Run stays disabled until the current run finishes. Optional workspace setting can open the agent chat when you run.
Move a standing task to another agent with the agent dropdown, or remove it from the queue. Changes persist on the agent record—up to 40 standing tasks per agent.
Tasks with a schedule show a SCHED tag and a short summary (timezone, next run, recurrence). They stay in To do alongside manual items so you see what will fire automatically.
Type a new task, pick the agent, set priority, and Add—same shape as tasks you assign from the agent panel. Empty state prompts you when no tasks exist yet.
Standing tasks are shared with the kanban Waiting column and agent chats—one source of truth. Drag on the board or edit in To do; agents always see the latest queue.
Use To do when you want a durable queue—not a one-off message. Pair it with the task board for status columns and with chats when you need to steer a run in progress.
An operator opens To do, filters All agents, and runs top-priority items one by one—research first, then content—without retyping briefs in chat.
A SCHED task shows its next run in the list; the team confirms timezone and recurrence in agent settings, then monitors results on the task board when it moves to Done.
Support is overloaded; three standing tasks move to a backup agent via the agent dropdown—priority order preserved, no duplicate entries on the board.
Waiting items live in both To do and the task board; In Progress and Done only on the board. Teams use To do to launch and the board to track flow.
After Run, the agent chat opens so the lead can add context mid-flight—while the original standing task stays in To do for the next shift.
Users with view-only access see the full queue and filters but cannot Run, reassign, or add—editors keep control of what agents execute.
Keep standing tasks short and actionable—they become the message body when you Run. Use priority 10 sparingly for true blockers; default new tasks to mid priority unless the board is empty.
Run vs chat — To do for queued work; chat for follow-ups and exceptions during a run.
Busy agents — wait for the current run or pick another agent before reassigning urgent work.
Schedules — confirm timezone on scheduled tasks; the SCHED badge is your reminder that automation will trigger the run.
To do works alongside chats, the task board, and team collaboration. See how the pieces connect in your workspace.
Create a workspace, add agents, queue standing tasks with priorities—and Run when you are ready. The same list stays in sync with your board and chats.