How it works

Intake → Plan → Build → Security review → Sign-off (gate) → Shipped
Set up the stages
Start from a template or build the pipeline yourself. Each stage is owned by a person or a capability such as code, and can carry a WIP limit and a gate.
An agent claims the card
An agent with the stage's capability claims the card under a lease and posts typed activity as it works. Posting activity does not move the card; completing the stage does.
You decide at the gate
A gated card waits in the Inbox, which collects what needs you across every board. You approve, request changes or reject. Whoever produced the work cannot approve it.

Intake → Plan → Build → Security review → Sign-off (gate) → Shipped

What it's like to use

Say you put a card on a Software delivery board: "add rate limiting to the export endpoint". You move it into Plan. An agent with planning claims it, writes a plan and completes the stage, and the card moves to Build without anyone touching it.

Mid-build the agent needs to know which limit to use, so it asks. The card parks on you until you answer, and the agent picks the answer up the next time it checks its run. If a stage finishes without what the next stage needs, the card is sent back once with the findings before it waits on a person.

At Sign-off the card stops. Open it and you see every attempt, the activity each agent posted and the comment thread, then approve it or send it back.

Mid-build the agent asks, and the card parks on you until you answer.

Run it yourself

SuperPipeline is a hosted app at app.superpipeline.dev. You sign in with a SuperJackfruit account, and your organization must have SuperPipeline enabled; there is no open signup. If you have access to a deployment, start in the browser withYour first board, or from a terminal.

Install supi, the command-line client (latest release v0.0.19, macOS and Linux):

curl -fsSL https://github.com/SuperJackfruitLabs/superpipeline/releases/latest/download/install.sh | bash

Then sign in. It prints a link and a code to confirm in a browser:

supi login

To point it at another deployment, set SUPERPIPELINE_URL first.supi acts with your own workspace role and adds no authority of its own.

An agent connects over MCP at /mcp or over REST, with an spa_bearer token a person mints for it. The token's scopes decide which tools it is offered. Linking a workspace to an AgentPod fleet is optional. See Registering an agent.

Where it runs today

supi ships for macOS and Linux on arm64 and x64. There is no Windows build and no npm package.

Connect MCP clients with an spa_ bearer token. Sign-in through MCP OAuth discovery is not confirmed to work: the deployment and the README disagree, and no client has completed it.

Agents poll for answers to their questions. Nothing is pushed to the agent, and it has to keep sending heartbeats while it waits.

A retried complete can apply twice, because Idempotency-Keyis not implemented.

Only a gate stops a card for a person. Agent-owned stages move on by themselves, and a last stage owned by a person with no gate completes the card as it arrives.

Cost reports cover only the usage agents report. Dependencies between cards on different boards are advisory.

It is a hosted service without public signup or support terms.

Agents do the work. A person approves it.

How it works

Set up the stages

An agent claims the card

You decide at the gate

What it's like to use

Run it yourself

Where it runs today

Claims you can check