Tasks.
A task is one piece of work an agent picks up and runs with. This page covers creating tasks, watching them in real time, following the streamed output, and reviewing the result when the agent is done.
The board
The Kanban board has six columns. Tasks move left to right as work progresses:
Backlog → To Do → In Progress → In Review → Done
↘ Blocked ↗
Drag a card across columns to move it, or use the + in a column header to quick-add directly into that column. While a session is active, cards in In Progress pulse; cards in Blocked show a red indicator.
Creating a task
The minimum is a title. Everything else is optional but improves the result.
- Title — one short line. Required.
- Description — the agent's only brief. See the next section.
- Priority — low, medium, high, critical.
- Assigned agent — pick from the agents configured on this project.
Quick-add: click + on a column header to drop an inline title into that column. Enter to submit, Esc to cancel.
Writing a description that works
The description is the only brief the agent gets — no prior context, no Slack history. Write it in plain words and end with the expected outcome.
- State the problem in one or two sentences.
- Say what "done" looks like: file added, endpoint returns X, button does Y.
- Mention any constraints (don't touch X, keep backwards-compat with Y).
If the description is vague, the agent will guess. If it's specific, the agent ships.
Priority
Four levels, surfaced as a colored badge on the card: low, medium, high, critical. Priority doesn't reorder the board automatically — it's a signal for you to triage when you have many cards waiting.
Moving work through the columns
Each column shows the actions available for a task sitting in it.
- Backlog / To Do — Start kicks the agent off and creates the task's branch.
- In Progress — Block pauses the session; Complete marks the task ready for review.
- In Review — View Diff, Merge & Close.
- Done — Reopen sends the card back upstream if a downstream test broke.
- Blocked — Resume restarts the session.
Live session output
While an agent runs, output streams to the task detail over SSE. You see what the agent is doing as it happens — file edits, command output, intermediate reasoning — without refreshing. The token tally updates as the run progresses and lands in the task stats header when the session ends.
Discussion and @mentions
Every task has a comment thread. Markdown is supported for the basics (bold, code, lists). To hand the task to a different agent mid-stream, type @ to trigger the agent dropdown, pick one, and post. The mention creates a new session for the named agent; a context summary from the prior session is shared in, and both sessions show up in the thread.
Review flow
When the agent marks complete, the card parks in In Review. Open View Diff to read the file changes, leave a comment, and either send the card back for another pass or click Merge & Close to land it.
Token tracking
Tokens in, tokens out, and estimated cost land on the task detail header when the run ends:
Tokens In: 12,345 Tokens Out: 67,890 Est. Cost: $0.0234
The same numbers roll up to the task card and to the assigned agent's lifetime totals.