1 · Intake
GitHub issues with trigger labels, repository todos, improvement suggestions, and PR comments all become work without a copy-paste step.
The software factory, self-hosted.
Work arrives as signals, becomes planned changes, runs in isolated build cells, and reaches GitHub for review and delivery. ProPR provides that line as free, Apache 2.0 software on your own server. Every unit is reviewable in GitHub, and you choose whether green pull requests wait for a human or use an explicitly enabled auto-merge policy.
What counts as a factory
- Intake that turns signals into work.
- Planning with visible scope and cost.
- Parallel, isolated build cells.
- Pull requests with execution records.
- A quality loop of review, CI, and follow-ups.
- Delivery through explicit merge policy.
- Telemetry spanning the entire line.
Overview
Six stations, one loop.
Each station is a ProPR screen or workflow you can open today.
01
Intakeissue, todo, comment
02
Planningscope + context
03
Build cellsisolated workspaces
04
Pull requestdiff + execution record
05
Quality loopreview, CI, follow-ups
06
Deliveryselected merge policy
Telemetry across the linePrompts, logs, model usage, cost, duration, commits, and recovery stay attached to each task.
2 · Planning
The planning station turns a prompt into scoped, review-sized tasks with the context and cost visible before anything runs. You approve the plan; approval is the handoff.
3 · Build cells
Every task runs in its own Git worktree, branch, and Docker workspace. Independent tasks run in parallel; nothing touches the main checkout.
4 · Pull request
Each completed run opens a normal GitHub pull request with its implementation summary and execution record. The branch becomes the shared surface for review, CI, and follow-up work.
5 · Quality loop
/review posts scored findings when requested; Ultrafix alternates review and fix passes until the score goal, the cycle limit, or a human stop. CI runs like it does for any branch.
6 · Delivery
Manual merges remain in GitHub. ProPR can auto-merge green pull requests only when you enable that policy. Larger changes can use an Epic-mode chain where each approved child PR merges before the next task starts.
Telemetry across the line
Every task keeps its prompt, diff, logs, model, tokens, cost, and duration on the dashboard and CLI. Those records show where the line is slow, expensive, or wrong.
You own the factory.
The whole line includes intake, planner, build cells, pull requests, quality loop, delivery, and telemetry. It is Apache 2.0 software running on a Docker host you control. The agents are Claude Code, Codex, Antigravity CLI, Mistral Vibe, or OpenCode, using your subscriptions or API keys with no token markup. The audit trail spans ProPR task history, Git commits, and GitHub conversations. Compare that ownership model with hosted agent-workforce platforms.
Repository policy closes the loop.
Each pull request exposes its diff and conversation in GitHub. /review adds a scored assessment when requested, and CI reports against the branch as usual. Manual merge keeps the final action in GitHub. Explicitly enabled auto-merge can complete a green pull request, including approved child PRs in an Epic chain.
A one-person factory, running in public since May 2025.
ProPR builds and maintains its own codebase through this delivery path. The public record includes 2,400+ pull requests opened, 2,100+ merged, and 690+ merged PRs building ProPR itself. The discussions, review scores, and merge history are open for inspection.