Pipelines

SuperClawd Pipelines turns your board into an autonomous pipeline. Assign a ticket and your own Claude plans it, works in an isolated git worktree, opens a pull request, and hands it back for your review — running locally, on the infrastructure you already have.

Prerequisites

You'll need Node.js (version 18 or higher) and a SuperClawd account. Pipelines runs as whoever is logged into the CLI on the machine, so run superclawd login first if you haven't (see One-Time Setup) — without a valid credential, Pipelines opens logged-out and serves no data.

Install

Pipelines ships as the @superclawd-ai/pipelines extension that the SuperClawd CLI launches. Install both globally with npm:

npm install -g superclawd
npm install -g @superclawd-ai/pipelines

Already have the CLI? Then you only need the extension — npm install -g @superclawd-ai/pipelines.

Launch

Start the local daemon from your terminal. It boots a server on your machine and opens your browser at http://localhost:63210.

superclawd pipelines start

The command runs in the foreground — press Ctrl+C to stop it. A few useful variants:

• superclawd pipelines start -d — run detached, in the background.
• superclawd pipelines start --port 7000 — use a different port.
• superclawd pipelines status — check whether the daemon is running.
• superclawd pipelines stop — stop it.

Only one instance runs at a time. Running start again while it's already up just re-opens your browser at the existing URL.

Connect a board

Everything in Pipelines lives under a workspace. Connect up to three of your SuperClawd workspaces, then bring in a board:

• Local board — hand-authored tickets, no integration. Every connected workspace gets one automatically.
• Vendor boards — import tickets from Linear, Jira, Asana, ClickUp, or Monday. Connections authenticate over OAuth through a hosted relay; the local daemon never holds a client secret.

Each workspace has a working directory — the folder Claude runs in for that workspace's tickets. It's often an umbrella folder holding several git repositories.

How a run works

Pipelines is an orchestrator, not a second AI. For every run it spawns your SuperClawd CLI, which launches real Claude Code with your directives, memory, and guardrails. A run moves through four stages:

1. Assign — delegate a ticket to a team or agent and choose an autonomy level.
2. Plan — Claude reads the ticket and writes a plan.
3. Work — it claims a repository, works in an isolated git worktree on a fresh branch (so concurrent runs never collide), commits, and opens a pull request.
4. Review — the card moves to In Review and waits for you. Nothing is ever marked Done without a human sign-off.

Runs are supervised or autonomous per assignment. In a supervised run, flagged actions pause for you on the board; in an autonomous run they're auto-denied and, rather than guess, the agent records an open question, blocks the ticket, and stops for a human. A hard floor always applies — no force-push, secrets, destructive actions, or auto-merge.

Schedules, PR monitor & API

• Schedules — run a saved prompt automatically on a cadence. Scheduled runs are restricted: they can investigate, write reports, and file board tickets, but can't modify code — code work is funneled back onto the board.
• PR monitor — an opt-in loop that watches a ticket's pull request after it reaches In Review, auto-fixing failing CI and optionally addressing review comments. It never moves a card to Done — that's always your call.
• Public API & webhooks — an optional key-authenticated HTTP API and signed event webhooks let you drive the board and react to run events from your own tooling.
• MCP server — enable it in superclawd config and Claude Code can drive your board directly (list/move tickets, add notes, start runs) — no manual setup while Pipelines is running.

Next Steps

Pipelines builds on the same building blocks as the rest of SuperClawd: