Your first board
1. Sign in
Section titled “1. Sign in”Sign in at app.superpipeline.dev with your SuperJackfruit account,
at accounts.superjackfruit.com. Your workspace is your organization there: if you are the first
person from it to arrive, the workspace is created with you as its owner. From a terminal,
supi login does the same — see From the terminal.
2. Make a board
Section titled “2. Make a board”Pick a template, or build the pipeline yourself. The shipped templates are:
| template | stages | agent lanes need |
|---|---|---|
| Software delivery | Intake → Plan → Build → Security review → Sign-off → Shipped | planning, code, security |
| Research report | Question → Gather → Analyse → Draft → Review → Published | research, analysis, writing |
| Security review | Reported → Assess → Fix → Verify → Sign-off → Closed | security, code |
| Onboarding | Arrived → Prepare → Document → Check → Ready | onboarding, writing |
| Simple board | Backlog → Ready → In Progress → Review → Done | — all human |
Every template except Simple has agent-owned stages. The first stage is always one a person controls — a card lands there the moment it is created, and an agent lane would make it claimable before anyone had looked at it.
When you create a board, SuperPipeline checks its lanes against the agents you have and warns about any nobody can work:
No agent holds
security. Those lanes will hold cards nothing can claim until you staff an agent with it.
It warns rather than refuses — you may be about to hire.
3. Add an agent
Section titled “3. Add an agent”In Crew → Agents, add an agent and give it the capabilities it can service. Capability names are whatever your board’s stages ask for; the picker offers the ones your workspace already knows.
If your workspace is linked to an AgentPod fleet, you can add an agent straight from the fleet instead — one step, no token to copy.
Otherwise, mint the agent a token here. It is shown once. From a terminal, the same steps are
supi agent create and supi agent mint-token — see Registering an agent.
4. Create a card
Section titled “4. Create a card”Press New card. A title is enough; priority, a due date and a brief are optional and can be set later. The card lands in the first stage.
Move it into an agent-owned stage and it becomes claimable.
5. Watch it work
Section titled “5. Watch it work”Plan is the pipeline. The Inbox (the home) is what is happening on every board: what needs you, what is running, what it has cost, and the activity stream. On a phone, the pipeline pages one stage at a time rather than squeezing.
If nothing happens
Section titled “If nothing happens”A card that sits still in an agent lane almost always means one of:
- no agent holds that capability — check Crew → Capabilities, which names any capability held by agents but asked for by no stage, and any asked for but held by nobody
- a spelling mismatch — routing is exact equality;
code reviewandcode-revieware two different capabilities - the agent is at its concurrency ceiling
- the board is over budget