Tasks
One queue for your own reminders and the agent work you have filed.
What this page covers
OutcomeFollow one task from the queue to a result you have actually checked.
Before you beginChoose the relevant project in Work so the board is filtered to it.
Follow these steps
The board is one list in four columns — queued, running, blocked, done — carrying both your own reminders and the agent tasks you have filed. Project filters it to one project at a time.
Only the queued column is yours to arrange: drag a card, or give it a priority. A high-priority agent task starts immediately instead of waiting to be run. Everything else reflects what the processes are actually doing.
Blocked is the column that needs you: an agent is waiting on an answer and nothing else about it will move until it gets one.
A finished card carries the reported result and whether its branch reached the branch it merges into — merged, or unmerged while the work is still only on its own branch. Opening the card marks it seen.
Example
Investigate why the audio test fails. Summarise the cause before changing code.
The card appears on the board and moves as the worker does. Open its terminal for the live work, and read the reported result rather than inferring success from the card having stopped.
A card is not the work
Every column but the queue reflects a process that actually exists, which is why nothing drags into or out of running: moving a card could not start or stop a worker. Cancelling is a deliberate click inside the card instead. The board can be a moment behind the process; it is never allowed to contradict it.
For the same reason, a card that stopped proves nothing on its own. Read the reported result, and for work that produced code, whether the branch merged — merged, or unmerged while it is still only on its own branch. Only an unmerged one is ever raised with you; “could not be told” stays quiet rather than crying wolf.
Edit reaches a queued brief only; a running or finished card refuses and says why. Remove from queue archives a queued task, Delete confirms and then drops the card for good, and neither touches a branch or a worktree. A branch that has fully merged has its worktree cleaned up in the background, separately.
Watch the work change state
One decision needs you. The rest keeps moving.
An illustrated example using Ginu’s task states.
Notes
- A worker exiting is not proof its task succeeded. Read the result, and the changes, before treating it as done.
- A card filed under a project is one of that project’s task lines. Filing it means naming which open line it is, so the board and the project file cannot drift apart.
Check
You can tell queued, running, blocked and done apart, and say why a stopped worker is not evidence that its task succeeded.