Who made this
Harrison Johnson, a product manager in New York. He has spent a decade building marketplaces and B2B software, as employee number one, as a co-founder, and as a product lead. He built productagent.dev with Claude Code and runs Loops on his own projects every night. Three pages come out of that work:
- 33 nights of unattended Claude Code: ten things that broke, what each taught, and why the morning review is the product.
- Eleven Claude Code asks: every problem from those nights, written as a spec with evidence, a way to measure it, and what to leave out.
- The receipts: the run record behind both, numbers only.
He also sets up productagent for product teams and runs the first two weeks with them. Past clients include deepgreen.co. Message him on LinkedIn.
Who productagent.dev is for
- Product managers who already run part of the day in Claude Code or Codex.
- Founders and operators with more projects than evenings.
- Anyone who wants an agent to keep working overnight without handing it the keys.
What you get: 10 harnesses
Each harness is a folder you can read before you run it. Open one to see every file.
- flow-design (global): A progressive design interview: one question per screen, ending in a clickable HTML prototype of a linear user journey (onboarding, checkout, wizard).
- loops (system): Give an agent a goal, a budget, a cadence and a model. It works one bounded run at a time while you sleep, inside a fence, and hands you four plain sentences in the morning.
- prototype-swarm (global): Crawls a multi-screen HTML prototype for undefined click destinations and spawns one generator agent per missing screen, with a handoff packet written by the source screen, until the click graph is covered.
- self-maintenance (system): The one way an unattended run may touch its own loop registry, and the one place a "need from you" becomes a decision you settle with a single command instead of a paste.
- rootcause (global): User research synthesis: groups interview notes, support quotes, board screenshots and metrics by root cause, separates symptoms from causes, and drafts the questions to ask next.
- show-dont-tell (global): Turns text-heavy docs and abstract ideas into accurate, code-drawn visuals: diagrams, charts, timelines, flows and comic strips that trace back to the source.
- pm-strategist (global): A product and strategy advisor agent that blends three lenses (build taste, business structure, PM execution) and pressure-tests ideas instead of cheerleading.
- todo (system): A TODO list for PMs in one markdown file, reachable from Claude Code and from Telegram: capture, see what's due, triage, and hand items to an agent that asks before it acts.
- rev-intel-harness ↗ (link): A CSV of companies in, the people out: point your existing AI subscriptions at target accounts. Open source, MIT.
- karma ↗ (link): A personal knowledge graph over everything the loops write: seeds in, relationships out, so a month of night reports stays searchable. Open source, MIT.
What Loops leaves you in the morning
## L-03 · Ship one fix
- Trying to: ship the "sort permits by county" backlog item.
- Did: added the county filter; the page renders in a headless browser.
- Decided: left the mobile layout alone; separate backlog item.
- Need from you: merge branch night/2026-09-14 if the screenshot looks right.Four words run the whole system. A Loop is work with a goal that renews itself. A Run is one bounded pass at a loop. An Order is a one-off instruction for tonight. A Decision is anything a run could not settle; the run hands the decision back to you instead of guessing. Read the full concept page at harnesses/loops/README.md, and the runner and fence at MACHINE.md.
