The system of record for product work — built for teams whose builders are agents.
Requirements, epics, acceptance criteria, and feedback live in one ledger. People decide; agents build; every action is attributed to both the person and the token that acted.
What it is
Pipebrain is a work ledger, not an orchestrator. It records intent, holds claimable work, and receives reports. Agents connect through an MCP server and consume the same API as every other client, so no surface quietly gains a capability the others lack.
- Requirements are living documents. Versioned, approved by a person, and delivered to every agent session automatically — always at the approved revision.
- Criteria are the contract. Each slice of work carries checkable acceptance criteria; machine-verifiable ones carry evidence, human ones require a signed-in person. The server enforces the gate.
- Attribution is structural. Every write records the acting person and the token used. Human-only actions refuse tokens outright.
- Secrets stay out of transcripts. Secret values move only through the CLI and the web UI — no agent tool can read one back, by design.
Install
The agent server and the CLI are public npm packages:
npx -y pipebrain-mcp # the MCP server (stdio) — register it with your agent
npm i -g pipebrain-cli # the ppb command — doctor, secrets, assets
Set PIPEBRAIN_API_URL and your PIPEBRAIN_TOKEN, then
ppb doctor to check the wiring. Full setup lives in the in-app guide
after sign-in.
Access
Pipebrain is invitation-only. There is no open signup: a member of an organization invites you by email, and the invitation is what creates your account. If you were invited, follow the link in your email; if you'd like an invitation, contact the operators.