Run an open-source software factory that merges hundreds of PRs from Slack

The Mastra team built Factory, an agent kanban board they tag in Slack to triage, plan, build and review work; in one week it opened and merged 238 PRs next to 630 from humans.

Done withCustom agentinSlackGitHub· Nov 18, 2026

What they did

The founders of Mastra, an open-source TypeScript agent framework, built Factory to help maintain their own codebase. It is a configurable kanban board of agents that anyone on the team can @-tag in Slack. Work moves through triage, plan, build, review and shipped. Under the hood it runs Mastra's durable agents for long sessions, a conversational memory, a markdown wiki with source citations that holds company knowledge, and signals that feed PR comments back into the running session. Each job runs in a cloud sandbox with their own coding harness. Senior engineers often start several sessions at once, for example asking it to triage the twenty oldest issues.

How it went

Across the mastra-ai GitHub org the team now merges hundreds of PRs a week. In the week before the post, Factory opened and merged 238 PRs while humans merged 630. Three months in, the team drives it mostly from Slack rather than its web UI. They also run bug and vulnerability scanners and closed the repo to outside pull requests, asking for detailed issue repros instead.

Worth knowing

This is the vendor describing its own internal use, and the Show HN post gives no defect or revert rate. Support for Claude Code and Codex as the harness was still in progress. A maintainer in the comments warned that agents also file plenty of correct but low-priority issues, so triage still needs a human sense of what matters.

Try it

With Custom agent· 3 parts to fill in

You are the triage and build agent for [my repo]. When someone tags you in [Slack channel] with a request, create a card on the board and move it through triage, plan, build and review. For triage, read the issue, reproduce it in a sandbox and say whether it matters for [our current priorities]. For build, work on a branch, run the tests and open a PR that links the issue. Watch the PR comments and push fixes when reviewers ask. Never merge your own PR: stop at review and post the PR link back in the Slack thread.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related