Seven projects built through pull requests.
A game started from nothing. A developer tool and a paid product built from plans. A business platform of more than 770 pull requests. A developer web app and a ten-year-old mobile app that kept shipping. And the website you are reading. All of their changes went through ProPR as issues, branches and pull requests.
Four of the projects carry their names and links. Two are private, described with their owners' permission and with identifying details left out. The named projects and this site are built by the developer who builds ProPR, shown as examples of what the workflow produces. The counts come from GitHub as of 11 November 2026.
Overview
Started from an empty repository.
No code yet. A plan became issues, and the product assembled one reviewed pull request at a time.
Claude Cope
A multiplayer terminal game, from an empty repository to 458 merged pull requests.
458merged pull requests, 412 written by agents Started from an empty repository on 1 April 2026 Read the case study
dig.vin
A paid product for used-car buyers, built from a written plan broken into epics.
185merged pull requests between 17 July and 11 September 2026 New product; first pull request merged on 17 July 2026 Read the case study
Agent Tank
A local dashboard for agent subscription limits, from an empty repository to a shipped tool.
56merged pull requests, 46 written by agents Started from an empty repository on 20 January 2026 Read the case studyA messaging-assistant platform
A conversational assistant with an admin console, onboarding, safety monitoring and analytics, built from one plan.
770+merged pull requests, 650+ written by agents Started from an empty repository in February 2026, still maintained through ProPR Read the case studyBrought an existing codebase.
Code with history, users and a way of shipping. ProPR joined it without changing any of that.
mcptest.io
An existing developer tool that has kept shipping through ProPR since ProPR's earliest versions.
200agent-written pull requests merged over sixteen months Existing code; first agent pull request on 16 July 2025, still shipping in November 2026 Read the case studyA ten-year-old mobile app
A consumer app for Android and iOS with a decade of history, taking new languages and bug fixes as reviewed pull requests.
110+agent-written pull requests merged Existing code, in production for over ten years; agent pull requests since mid-2025 Read the case study
propr.dev, this website
The site you are reading, run through issues, epic branches and second-model review since June 2026.
113merged pull requests, 76 opened by agents Existing site, hand-built in April 2026; every change through ProPR since June 2026 Read the case studyWhat the seven have in common.
A game, two products, a developer tool, a business platform, a decade-old app and a website share one path for their changes, and that path keeps AI-built software easy to steer whether the project is a week old or ten years old.
- Write down what you want.For a new project, a plan describes the product and ProPR turns it into small issues written in plain language. For an existing codebase, the backlog already holds the issues.
- One pull request per issue.An agent works on each issue on its own branch and sends back a pull request with the proposed change laid out for you to read.
- Review, then merge.Related pull requests collect in an epic, a branch for one feature. Nothing reaches the product until you merge, and GitHub keeps every merged pull request in the history with a Revert button.
How the workflow works · The public record of ProPR's own pull requests · Build something: six walkthroughs
Start your own.
ProPR Hosted runs everything for you; connect GitHub, describe what you want, and review the first pull request in your browser. Or try the live demo first.
See ProPR Hosted →If you are new to GitHub, Your first AI pull request, start to finish explains every word, and self-hosting on your own server is free and open source.