Help: the pipeline¶‹ PreviousNext ›
The Pipeline (on your Home, and in the Toolbox) is the project's list of work waiting to be done: ideas you parked, questions for you, and work passed between you and your AI agents. Tap a box to see what can be done there.
For creator and pro projects: you and your maker¶
You and your AI. Tell it what you want and it builds it; when there's no time now, say "park it" and it goes on the list. The list is the pipeline: each idea or to-do is an item, new until your AI (or you) takes it, then done. Your AI asks you when it needs a decision, and you can drop anything you don't want. That's all there is to it.
The map at the top of your Pipeline page (creator projects; sample data here): you on the left with what's waiting for you, the pipeline in the middle with its items by status (a pill each: new, in progress, waiting, review), your AI on the right, coloured by what it's doing (as on the Agents page). Tap a part to see its items; How it works comes back here.
For master projects: roles and agents¶
Master projects add specialist roles (designer, coder, tester, guardian) and their agents, the Agents page, handovers and the MCP server; see Agents.
A guardian agent watches the changes in its areas and reports what it finds, as items for whoever made the change; it never fixes another role's work (being designed). How to run agents, guardians included: Agents.
The map at the top of your Pipeline page (pro and master projects; sample data here): you, then each role in turn (designer, coder, the tester while it's testing, the guardian), each coloured by what its agent is doing and topped with its items by status. Tap a role to see its items (and its agent's).
Parking an idea¶
Say "park it" to your AI about an idea and it becomes an item for you, with your words at the top of its document. You can also make one from the Pipeline page (New item). An item has a title, who it's from and who it's for (a role, and a person), a kind (question, design, code, test, handover…) and a document that grows as people and agents work on it.
From → for, and who took it¶
Each row shows who → whom: the role that made it and the role it's for, with a name when it's for someone else. Opening an item shows its document, where it came from, who took it and when, and its history. The items you have to act on yourself (for you, waiting on your answer, or an approval) stand out in the list and come first; your agents' items don't.
Taking, statuses and Done¶
Take it makes an item yours and puts it in progress. Set its status as the work goes (pending, waiting, waiting on someone's input, done) or press Done. Your own items have a ✓ on their row in the list: one tap closes it, and Undo puts it back for a few seconds. Only the person an item is for, or their AI for one of their agent roles, takes and finishes it.
Important items¶
Tick an item's Important box (on the list or the item's page) and it goes to the top of the list, and your agents take it before anything else for their role. You mark items important, or your AI does when you ask it to; agents see the ★.
The list's order¶
Important items first, then what's in progress, then what's yours to act on (it stands out), then the rest, newest change first; done items last. A follow-up or an item waiting on another sits indented right under it.
Next up: rank, size and batches¶
Open a role (tap it on the map, or Next up on its view) to see what its agent will take, in that order, numbered. Move an item with ↑ ↓; a handover and important items always come first. Each item has a size (S, M, L; change it on its page): an agent that takes a small item also takes the small ones right after it, up to five, marked taken together.
Taken means locked: follow-ups¶
Once someone has taken an item, only they change it. Anyone else who wants something changed makes a follow-up (the button on the item's page); it links to the item, and whoever took it is told.
Waiting on other items¶
An item can wait on other items. When the last of them is done it becomes new again and its person is told, so an agent working the pipeline picks it up.
Handovers between chats and agents¶
When an AI's conversation gets full, it writes a handover item for its own role (where things are, what's next) and parks one for you: "Start a new chat as the coder". Start the new chat with "You are the coder. Work the pipeline."; it takes the handover, which closes the start a new chat item by itself.
To-dos and items side by side: Work¶
The Work page (/work, first tile of the Toolbox) shows the to-dos written in your topics on the left and the pipeline's items on the right, in one band per feature (a to-do's feature is the {#id} of the section it's under; an item's is its feature), with whatever has no feature in Unsorted, last. Flat shows one list per column instead.
- Promote a to-do (also To pipeline in the Backlog): it becomes an item with its text and feature; the to-do stays, ticked, with a link to the item, as your draft of that topic.
- Move to to-do an item that should wait: it becomes a to-do in a topic you pick (by default
ToDo:PROJECT, under From the pipeline, made if missing; Parked: needs more thinking is for to-dos you park by hand), as your draft, and the item is closed as moved to to-do, linked to its to-do. (Parking is the other way round: an idea becomes an item for later.) - Promoting and moving to to-do are your calls. Your AI does them when you ask it to (it names you as the one who asked, and the item's history says so); otherwise it suggests: an item for you, kind
suggestion, listing what to promote, move to to-do or drop, each linked, and you decide on the Work page.
Only people move work between people¶
Your agents work for you: they take items for their own roles and hand them on to your other agents. Passing an item to another person, or moving it to another project, is always a person's decision.
See also: Help, the system view.