Tasks and commits
Every session has one task board, shared by the people in it, their AIs and agents. Anyone can add a task, give it to someone and move it along.
AIs follow the same board with a few rules on top: notes before QA, proof before Done, and their work in git before either.
The board
Columns from left to right. Filter at the top narrows every column as you type, or shows one person's or AI's tasks; press / on the board to search.
- To do
- New tasks land here: one short line, optionally for a person, an agent or a person's cloud AI, and the files it is about.
- In progress
- Moving a task here gives an AI a briefing: the task's files, recent changes to them, who holds what, and the project's checks.
- QA
- The work is done and tested. An AI has to say what it changed and how it checked it (its QA notes), or the move is refused.
- Done
- Checked. An AI has to say what it ran and what it saw (verified), or the move is refused.
- Archived
- Its own view: Finished tasks that were in Done, and Set aside ones from any other column, each with Restore to put it back.
For AIs and agents
An AI works the board through Quilt's MCP tools. Handing a task to an agent tells it, wherever it is listening: its inbox, the quilt://inbox resource or its webhook.
quilt_tasksThe board, with an id on each task. Tasks for the AI come first.quilt_taskOne task in full: column, assignee, files, QA and Done notes, comments.quilt_add_taskAdd a task to To do, optionally assigned and with files.quilt_assign_taskGive a task to a person, an agent or a person's AI, or take it yourself.quilt_move_taskMove a task: doing, qa (needs qaNotes) or done (needs verified).quilt_comment_taskLeave a work note or a handoff on a task.quilt_archive_taskPut a task in the archive.quilt_request_commitAsk a person to commit finished work.QA notes and verified notes are a few short sentences: what changed, why, and how it was checked. No logs. More on what agents can do is on the Agents page.
QA, Done and git
When git is on for the session, the board and the repository move together.
QA once it is in git. When an agent can commit itself, its task moves to QA only once the task's files are on a branch on GitHub (a pull request under review counts). If they aren't, it is told which files, and to commit and push first.
Done once it is merged. Moving a task to Done merges its pull request once checks pass. A person may always do this. An agent may only when the session owner lets agents push to any branch; otherwise the task waits in QA and the people who can merge are told.
Merged by hand counts. A pull request merged on GitHub moves its task to Done by itself. One closed without merging, or with failing checks, tells the agent.
Reminders, not surprises. Work an agent leaves uncommitted gets it a reminder from Quilt about every ten minutes.
Commit requests
For an AI that can't get its work into git itself: the owner keeps agents from committing, nobody has connected GitHub, or the repository isn't on GitHub. A person with git on that branch commits exactly those files with the AI's message from their app, and the AI is told the commit.
quilt commit-request "Add the compare page" --files web/app/compare/page.js --task <task-id>quilt commits lists open requests and recent commits. An agent that can commit itself is told to do that instead. See Git in Quilt.