Open source · built on Claude Code
A product development agent.
productagent does the product work as well as the code: user research, design, prototypes and fixes. It keeps going overnight, on a budget, on the Claude subscription you already pay for.
pm/nights/2026-09-15.md
## Permit research, iteration 2
- Trying to
- read the second of five county permit files.
- Did
- read all four documents. The permit says 96 units; the agency page says 98. Flagged it, didn’t guess.
- Decided
- one row per permit, not per building.
- Need from you
- check the renewal on the state portal. It needs a login the fence denies.
41 min · $3.80 of $6 · 0 pushes · progress: yes
01 / What’s in it
Three parts.
One agent.
Loops
Give it a goal, a cadence and a model. It works overnight on a night branch and leaves a four-line report with the calls that are yours.
Budget
It runs on the Claude subscription you already pay for. You set a time limit per run and spending caps per week and month. Every report says what the night cost.
Skills
A library for the product work around the code: user research, design, prototypes, strategy. Each skill is a folder you can read before you run it.
02 / Skills
Product work.
Written down.
User research
- rootcauseGroups interview notes, support quotes and metrics by root cause, and drafts the questions to ask next.
Design
- flow-designA design interview, one question per screen, that ends in a clickable prototype.
- prototype-swarmFills in every missing screen of a prototype until each click goes somewhere.
- show-dont-tellTurns a wall of text into diagrams and charts drawn in code.
Strategy
- pm-strategistA strategy advisor that pressure-tests an idea instead of cheering for it.
Running the day
- todoOne TODO file you can reach from Claude Code and from your phone.
Copy any skill folder into ~/.claude/skills/. The full list →
03 / Who it’s for
Small teams.
Long projects.
Founders validating a business
You have an idea and no team yet. It does the research and the prototype while you talk to customers.
Solo builders
You are the PM, the designer and the engineer. It keeps the work moving on the nights you can’t.
Small teams
A product you plan to run for years. Loops keep the recurring work going and the budget stays inside the plan you have.
04 / Loops
It works at night.
Inside a fence.
A goal, not a prompt. Every loop has a definition of done and a review date.
A night branch and an OS sandbox. It never pushes or deploys.
A time limit per run. Spending caps per week and month.
Parks itself after two stuck nights, and tells you which calls are yours.
05 / Where it fits
Not another
agent sidebar.
| Tool | What runs | When it stops to ask |
|---|---|---|
| Conductor-style apps | Parallel agents on your Mac, while you watch | You decide live |
| Claude Code scheduled tasks | A prompt on a schedule or trigger, in the cloud or the Desktop app | Up to your prompt |
| Loops | A product goal on your Mac, inside a fence, built on Claude Code | Built in: done checks, parking, “Need from you” |
Loops runs on Claude Code. It adds the management layer for unattended product work.
06 / Straight answers
Short questions.
Short answers.
What does it cost?
Nothing extra. It runs on the Claude or ChatGPT plan you already pay for, under caps you set.
Does my laptop stay on?
Plugged in, lid open or shut. It runs in the first window your Mac is awake and on power.
How do I know the report is true?
One command in the morning has a second model check the report against the actual diff.
Can it be shut down or acquired?
It’s MIT-licensed files in your repo. There’s nothing to shut down.
Only code?
No. Any goal that ends in files: research, docs, HTML prototypes, fixes.
Windows or Linux?
Not yet. macOS only.
07 / Install
One line.
Four questions.
INSTALL LOOPS · MACOS · RUNS ON THE PLAN YOU ALREADY PAY FOR
curl -fsSL https://productagent.dev/install.sh | bashPuts the machine in ~/loops, notices that Claude Code is there, asks what to work on, how often, how much brain and what it may spend, then writes your first loop. Nothing runs until tonight, and only if the laptop is plugged in. Stop it any time with --off. Nothing phones home.
Don’t have Claude Code yet? Do this first.
Claude Code is the terminal version of Claude. Loops runs it for you overnight on a Claude Pro or Max plan, the one you already have. Open Terminal (press ⌘ space, type Terminal, press return) and paste:
curl -fsSL https://claude.ai/install.sh | bashThen sign in once. Type claude and press return: a browser tab opens; sign in with the same account you use in the Claude app, then type /exit.
WHAT HAPPENS AFTER YOU PASTE IT: FOUR QUESTIONS
Installing to ~/loops wrote pm/CHARTER.md wrote pm/LOOPS.md (empty) wrote .claude/settings.json (the fence, with your paths filled in) Armed. The checker looks every ten minutes; nothing runs until you write a loop. Loops · your first loop Four questions. One file gets written. 1 · Which agent runs the night? both are installed 1) Claude Code per-path fence; can read the web 2) Codex sandbox with the network off; harder no-push choose [1] 1 2 · What should it work on? pick a number, or type your own 1) Watch three competitors' changelogs. Tell me what changed. 2) Ship one small fix from the backlog. Verify it renders. 3) Read yesterday's support tickets. Name the top three themes. goal [2] 2 3 · How often, and how much brain? cadence [every-2nd-night] ⏎ brain: fast (Sonnet) · deep (Opus) · frontier (Fable) brain [deep] ⏎ 4 · What may it spend? per run [6] ⏎ total for this loop [48] ⏎ at most $90 a month at this cadence; ends after 8 runs Written pm/LOOPS.md (L-01, review by 2026-10-30) Trusted ~/loops in ~/.claude.json (so the fence's allow rules apply) Dry run every guard, no model call, no spend tonight the machine would run L-01. ✓ Tonight plug the laptop in. Lid open or shut. Morning read pm/nights/<date>.md
08 / The agency
Or have it set up for you.
I install productagent for your team and run the first two weeks with you. Past clients include deepgreen.co.
Message me on LinkedIn ↗Setup · two weeks
- Install Loops on your repo, fenced for your team.
- Write your first three loops together.
- Pick the skills your team needs and tune the budget.
- Review the first week of mornings with you.
09 / The record