build
Loop HQ
How I build my products with AI: builder agents, separate reviewers, and nothing ships until a person signs it off. Used across six products.
the problem
I was building with AI and running parallel tasks that just weren't moving fast enough.
why it hurts
One person cannot watch many AI sessions at once, and a builder left unchecked will report work as done when it is not.
what i built
Loop HQ: one overview session hands work to many Claude Code cloud sessions across six products, builders are checked by independent reviewers, there are hard stops before anything reaches production, and one screen shows every session. I designed it and run it.
how it works
Keep builders and reviewers apart.
whyThe reviewer runs on a stronger model and is asked to find what is wrong. It caught a builder falsely claiming a staging environment was missing, and a change that would have shifted a live button.
Stop at a pull request.
whyShipping to production is never the loop's call, so it can run for hours unattended without putting the live product at risk.
Stop when a check fails.
whyA task that fails a check twice stops and reports, the loop winds down at 90 per cent of a usage window, and hooks block unsafe pushes.
in detail
One loop, checked at every step, and one screen that shows every AI session in it.
Every change takes the same path
Plan, build, independent review, a person decides, then main. Here the Slurrp Farm loop has parked a round after its second retry was contradicted: nothing landed and nothing was spent.
Guards, caps and a person at the end
The guard counts what it blocked and refused, a watchdog raises alerts, and the Prizerv loop wound down at 90 per cent of its five-hour usage window. Work that needs a decision waits under "You decide".
Every session is a person
Each Claude Code session sits at a desk in its project's room. The overview session walks each real message to the desk it is for, and the exchanges run down the side.
The loops, room by room
Each loop's roles at their desks, with plan, build and review along the top row. Anyone who needs a person waits at the door, on the orange mat that stands for you.
One data feed behind every view
Watcher scripts write one file, status.js. The page reads it, replays it as a live feed, and changes nothing in any repository.
The real Loop HQ page and its data from 27 September, shown at that time.
why it's useful
Products get built at speed because builds run in parallel, and only checked work lands. The AI does the relentless, repetitive work on code and tests; I keep product, taste and decisions. About fifteen sessions worked through the night of 27 to 28 September.
technical specs
- One overview session holds the task list across six products and briefs Claude Code sessions, local or in the cloud, running in parallel.
- Every change takes the same path: a brief, a builder on its own branch, tests written first, an independent verifier on a stronger model, one fix round, a pull request, and a person who merges. A task that fails twice stops and reports.
- Guard hooks block writes to a production database, reads of secrets and unsafe pushes, and a usage ledger winds the loop down at 90 per cent of the five-hour window.
- Watcher scripts write one feed, status.js, once a minute. The page draws it as a pixel office and a terminal view, and only ever reads it.




