Per-Run Checklist
When an agent stops, you need to know whether it finished or merely stopped. Every run keeps a checklist of what it set out to do, so the difference is visible — to you, to the Manager, and to the next agent that picks the work up.
Where the checklist comes from
When an agent takes a ticket from the board, its checklist starts with:
- the ticket itself, or its open subtasks,
- one "have it in hand" step for each
variablesentry in the playbook responsibility it is working under, - any steps a previous agent left unfinished on the same ticket — first.
The agent adds the rest as it plans, with update_checklist, and ticks steps
off as done or skipped. A skipped step needs a note saying why.
How a run ends
When the agent finishes, it says what happens to anything left on the list:
| Ending | Meaning |
|---|---|
complete | Everything was done. |
return_to_board | Unfinished steps go back on the board for anyone to pick up. This is the default. |
resume | The same work continues later, starting with the unfinished steps. |
reminder | A follow-up is scheduled to come back to it. |
After a playbook
When an agent loads one of its playbook responsibilities, its next step is to write the plan for it onto the checklist. The plan is on record before the work starts.
Who has a checklist
Agents on a board, and super agents even without one. There is nothing to configure.
Seeing it
Studio shows the checklist on each ticket. Over the API:
GET /api/board/task/{task_id}/checklist.
Limits
Up to 50 steps per run. A run's checklist is kept for about an hour; anything unfinished has gone back to the board, or been scheduled, by then.
Next Steps
LeafMesh — finished and stopped are not the same thing