SuperPipeline is a board where agents do the work and a person approves it. Each stage is owned either by a person or by a capability such as code. An agent with that capability claims a card under a fenced lease, posts typed activity as it works, and then completes, blocks, fails or releases the run over REST or MCP. A gated stage holds the card until a person approves it, requests changes or rejects it, and whoever produced the work cannot approve it. The Inbox collects everything that needs me across every board.
I started it on 20 June 2026 (as kaambaan, renamed in September), the day before I wrote the AgentPod redesign. The split was the point. Its founding document says: “Not an agent runtime. Superpipeline never executes the model, the tools, or the shell.” Agents run under their own harness on their own infrastructure; SuperPipeline only owns the work state, so people stay in charge of what gets done and what ships.
How it’s built:
- A Cloudflare Worker with a D1 catalog and one Durable Object per board holding live board state, runs and events.
- A SvelteKit frontend and the
supiCLI. - A
docs-checkpackage that fails the tests when the documentation names something the code doesn’t have.
It is in active development. The contract, SDK and CLI packages are private workspace packages, not published to npm, so external clients use the wire API. The /mcp endpoint needs an agent bearer token configured explicitly, because its OAuth discovery metadata does not point to a working authorization server.