Every card is a file.
A task is a .task.tsx beside the work it is about: its status, priority, due date, who holds it, and a readme with the details. People and agents pick up the same cards.
A task in one element.
One of CommandAGI's own tasks, as stored in its Drive. The board, an agent's tool and your editor all read and write this line. Its readme is the .md file beside it.
One rule for two edits. When two people or agents change a task at once, the newer status wins and their claims merge (docs/sync.md § rule 1). Nobody sees a conflict.
export default () => (
<task id="agent-services-first-step" title="List the live offerings and the open requests" status="todo" priority="medium" projects={["agent-services"]} dueAt="2026-11-07" readme="List the live offerings and the open requests.md" />
);Counted in the Drive
52 tasks, each one a file.
CommandAGI runs its own work on these cards. Most sit in the inboxes of its roles; the rest belong to its initiatives, one project each. The study counts who holds a task and names nobody.
.task.tsxfiles- 52
- to do, 6 done, 4 blocked
- 42
- at high priority, 20 with a due date
- 9
- with a readme beside them
- 52
cloud://home/user-commandagi/**/*.task.tsx (production)Output case-studies/tasks/stats.jsonTool scripts/sites/case-studies.mjs tasksRan on This computer (dell-gb10-1), reading the production DriveWhen Put your work on cards that are files.
Ask an agent to pick one up, or open the board yourself.