
AGENTS.md or a skill, and all 9 agents follow it.AGENTS.md come after. Human review is the smallest layer at the bottom. A factory built on a messy repo is a fast way to make more mess.We set up software factories on your stack: CI gates, review agents, QA on previews, Sentry-to-PR fixes, changelogs and SEO, with your developers and on your real tickets.
| Job | What starts it | What the agent does | How you check it |
|---|---|---|---|
| PR review | Every PR | Comments on bugs, security holes, broken conventions | You accept or ignore the comments |
| QA | Every preview deploy | Clicks through the changed flows with Playwright, records a video | You watch the video |
| Errors and logs | Groups duplicates, finds the cause, opens a fix PR with a test that reproduces the bug | The error stops coming | |
| Changelog and help center | A merged PR or a release | Writes the changelog entry with screenshots, updates the help articles the change touched | Read it, 2 minutes |
| SEO | A weekly audit, Search Console data | Fixes broken links, meta tags, slow pages, writes articles from real search data | The audit passes, pages get indexed |
| Customer requests | A support email, an Intercom chat, a Slack message | Turns it into a ticket with steps to reproduce, fixes small ones, drafts the reply | The customer confirms |
| New features | A ticket moved to "Ready" in Linear or GitHub | Writes a plan, builds it, opens a PR | You review the result on staging |

Anything that says the software should change: a Linear ticket, a Sentry alert, a failing CI job, a customer email, your own idea. Most factories start with people filing tickets. The good ones also listen to production.
An agent checks if the signal is real, if it's a duplicate, and if it's clear enough to build. Our rule: if a ticket doesn't have acceptance criteria that code can check, it goes back instead of getting built. This is the slowest part of the whole factory, because most backlogs are full of tickets like "improve onboarding" and nobody volunteers to rewrite them.
Before writing code, the agent writes down what it will build and how to check it's done. A person approves it in the ticket. A misunderstanding caught here takes 2 minutes to fix. Caught in review, it takes a day.
The agent builds in a fresh sandbox with no production credentials, in a fresh session. Every step gets a new agent, so context doesn't rot and one confused session doesn't poison the next. Put a budget on it: 2 CI attempts per run is enough. If the second one is still red, the run stops and leaves a report in the ticket instead of trying forever.
The builder never grades its own work. CI decides if the work passes, not an agent saying "tests pass." Then a separate review agent reads the diff, and a QA agent clicks through the change on a preview deploy. Two rules worth stealing:
This is your job. You look at what changed, not how. More on this below.
Merge, deploy, and let an agent write the changelog entry and update the help center.
Errors, logs, support tickets and analytics flow back as new signals. When something breaks, trace it to the PR that caused it. Factory does this every night. It's also how you find out whether your checks work: if the review agent approved something that later broke, you know what to fix in the factory.
PostHog calls this self-driving: agents watch production, and when one finds a problem, another opens a PR. In October, 11% of their merged PRs started that way. A person still merges every one.

CLAUDE.md or AGENTS.md: how to run the app, how to test it, the patterns to follow.If a new hire can't run your app and its tests on day 1, an agent can't either. Most teams find out their factory problem is a repo problem this week.
agent-ready. Tickets with that label and clear acceptance criteria go to the factory.We'll build the loop on your repo, your tracker and your monitoring, start with the safe jobs, and hand it over with the numbers that show what changed.

| Type | How it works | Use it for |
|---|---|---|
| Dark factory | Takes a loose request, plans, builds, reviews and merges to production with no human | Prototypes and throwaway proofs of concept. Nothing with users. |
| Fleet factory | Same automation, but only for work with a clear, testable goal | Migrations, dependency upgrades, refactors, cleanups |
| PR factory | Agents build each ticket, you review every PR | Getting started, or code where mistakes are expensive |
| Release factory | You plan 10 to 20 tickets together, agents build them in parallel, you review the batch on staging | Most product work, once your checks are good |
| Self-improving factory | A release factory that also turns production errors and analytics into new tickets | When you trust the loop and want it to fix what users hit |
CLAUDE.md or AGENTS.md, and enforce it with lint rules, not prose. A lint rule the agent can't skip beats a paragraph it can ignore.Loading editor...
## What changed One sentence a customer would understand. ## Why Link to the ticket, the Sentry issue or the customer request. ## Changed surfaces Write "None" under a heading when nothing changed there. ### Database | Table | Change | | --- | --- | | `invoices` | new column `paid_at`, nullable | ### Migrations | Migration | Does | Data | Risk | | --- | --- | --- | --- | | `20261117_add_paid_at` | adds `paid_at` | backfills from payments | low, runs in under a minute | ### Screens | Screen | Change | | --- | --- | | `/app/invoices` | new "Paid on" column, filter by paid date | ### Customer communication | Channel | Change | | --- | --- | | Email | "Invoice paid" email now shows the payment date | | Web notification | none | ## Before / after Screenshots of every changed screen, desktop and mobile. ## Video 30-60 seconds of the agent clicking through the flow on the preview. ## How it was checked - [x] CI green on first or second run - [x] Review agent: 0 blocking comments - [x] QA agent: flow recorded, no console errors ## Risk Low / medium / high, and what to look at if it's not low.

Agent instructions, lint rules, fast CI, preview deploys, a PR template with screenshots and video, and AI review on every PR. We do it with your developers, so they keep it running.
| | Local factory | Remote factory |
|---|---|---|
| Runs on | Your laptop, in an app | A server or the cloud |
| Runs when | Your laptop is open | Always, triggered by webhooks and schedules |
| Pays with | Your Claude or ChatGPT subscription | API usage, Team seats, or a subscription on a VPS |
| Good for | Solo founders and small teams, doing your own tickets faster | Teams, work that starts without a person (errors, PRs, releases) |
| Examples | Claude and Codex desktop apps, T3 Code, Conductor | Claude Code scheduled tasks and GitHub Actions, Capy, Factory, a VPS |





| Metric | What it tells you |
|---|---|
| Regret-free merge rate | Share of agent PRs that merged and didn't need a revert or a follow-up fix. The main number: climb it until you can automerge. |
| Share of merged PRs by agents | Kaching is at 77%, PostHog at about 70%. |
| Merged PRs per day | Kaching went from 10 to 39. If this doesn't move, the factory isn't working. Count merges, not PRs opened. |
| Bugs traced to agent PRs | Compare with bugs from human PRs. When agents break things less often, give them more autonomy. |
| Cost per merged PR | Tokens and compute divided by what merged. Not per run, per merge. |
| Time from signal to merge | How long an error, a request or a ticket waits before it's fixed. |
We set up the whole loop on your stack: agent-ready repo, CI gates, AI review, QA videos on previews, Sentry-to-PR fixes, changelogs, help center and SEO. Your team keeps it, and the numbers show what it changed.
Focus on customers and sales while we handle product delivery. Hire a dedicated AI maker or a whole product team.