
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.| 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 |



| 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.

| | 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. |
Focus on customers and sales while we handle product delivery. Hire a dedicated AI maker or a whole product team.