vibes.diy/docs Make an app → Discord
Engineering log

How three people run a product with a night shift of agents

Vibes DIY is three people: Chris, Meghan and Marcus. At 12:42 every night, Pacific time, a chain of scheduled Claude agents starts working on the product, and by 6:00 in the morning there is one page waiting that says what the night did. We call the whole arrangement the software factory. Chris's read on the result is that our conversion rate has more than doubled since we started working this way.

Title card in deep green: the words night shift, an arrow, and note by 6 in bright pink above the post title, over a faint drawing of a desk lamp, a window with the moon in it, and one sheet of paper.
The night shift works in order, and the last job writes the note.

A goal is a job that never finishes

The unit of the factory is a goal: a standing objective with no done state, run on a schedule. Each run reads where things stand, does the most useful piece of work it can finish, writes down what it did where the next run will find it, and exits. The agent starts fresh every time and reads the last run's note first, so the plan lives in the open where the team can read it too.

Each goal is one plain document, and the schedule's whole prompt is one line telling the agent to read that document and run one cycle. Changing what a job does means editing its page, with the same review as any other change.

Every job also names which of six outcomes it serves. Four follow the path a person takes: a stranger starts a real app, the app they get is good and it's theirs, the app brings its people, and makers come back. The fifth is that we can ship any day and everything apps rely on keeps working. The sixth is steering: money, legal and rules all stay handled, and the team knows what's new.

What the factory listens to

The factory builds from four streams of input, and the first one is us talking.

  • Team meetings. Our meetings are transcribed. A job reads the transcript and the meeting notes, writes up each thing we agreed to as an issue, assigns it to Chris, Meghan or Marcus, and posts a short summary in the team chat. Product and customer calls go through it. Board, investor, legal, accounting and recruiting calls stay out, every time. So a sentence like "that button should say what it does" turns into a piece of work with an owner by the next day.
  • Visitor sessions. A nightly job reads how yesterday's new people got on with the product: where they started, how far they got, what they reached for. Each finding is filed with where on the path it happened.
  • The inbox. Every two hours during the day a job sorts Chris's mail. A customer question gets a reply drafted for him to send, and a report of something broken becomes an issue.
  • Our own answers. When a job needs a person's call, it asks on one page, and the next run reads the answer back.

Get posts like this in your inbox

One email field. Real updates. No algorithm required.

Live conversations feed it too. A working session with an agent is for talking, designing and looking at options. The build gets filed as an issue, and the factory picks it up on its next run.

The night, in order

The jobs run as a chain, staggered so each can use what the one before it found.

Pacific timeJobWhat it does
12:42 AMShip watchNotes what went live yesterday, so every later job knows which fixes people already have.
12:59 AMSession digestReads yesterday's new sessions and files what they show.
1:11 AMClick-throughMakes a fresh app, shares it, and opens the link the way the person receiving it would. Then walks each recent change on the live site.
1:45 AMTriageGroups the findings, merges the fixes that are clear, and prepares side-by-side options where the answer is a matter of design.
2:45 AMIssue builderSorts every new issue and builds the bugs and small changes. It runs again at 1:45 PM for what the morning filed.
From 3:30 AMHousekeepingThree jobs in a row: lessons the agents wrote down get folded into the team's docs, old pull requests are finished or closed, and the code is swept against our own rules.
5:35 AMMorning reportReads every job's notes and writes the day's page, ready by 6:00.

Over four nights in mid-November the chain took between 4 hours 1 minute and 4 hours 39 minutes from the first job to the last. Up to four builder agents work at once, which is what the shared machine holds comfortably.

Merging a fix and putting it in front of people are separate steps. Twice a day, at 8:05 AM and 2:05 PM, a ship job checks its list, presses the button if everything is clear, and stays with the release for two hours afterward.

One page for the questions

Most of what the factory decides, it decides and reports. Two kinds of question go to a person, and both go to one page we call the feedback desk, which Chris opens on his phone.

A hold is anything with real consequences: sending email, spending more than a small amount, privacy, deleting something. A hold waits for a yes, however long that takes. A taste question is a design call, such as which of two looks to keep or a line of copy that makes a promise. Each question arrives with a short paragraph, screenshots when the choice is something you look at, and answer chips, with the agent's own pick shown in gold. A taste question that sits for two days goes with the gold pick, and a later answer still wins while the change is easy to undo.

When the issue builder is unsure whether we'd want a change, it builds it anyway as a draft and asks "merge this draft?" with a link to try it. Clicking through a working version settles the question in a minute.

A council of judges

Design has no test that passes or fails, so for some work we make one out of judges. Several AI models from different companies each score the same thing, blind: our home page's first screen sits shuffled and unlabelled among other app builders' pages, and the judges are never told the score we hope for. The agent fixes what they flag and asks again. In one day that loop took our first screen from 5.7 to a best of 8 out of 10, and Three AI judges helped write our home page tells that story.

The same shape checks our ads. Image models sometimes misdraw letters, so every ad image is read by two judges from different companies before it goes out, and either one can send it back for repair.

The rules that let us sleep

A few rules apply to every job.

  • A stop switch. One of us can pause the whole factory from a phone. Every job checks the switch before its first write, and a job that can't read the switch treats it as on.
  • Notes in the open. Each job keeps its running record in one place and stamps the time it last ran, so a quiet job and a stalled one look different. The first job of the night checks every stamp and tells us about any job that has gone quiet too long: 36 hours for a nightly one, 16 for the issue builder.
  • One message a night. The chain posts a single summary to the team chat, one line per job that had something to say. A job speaks up on its own only when it needs a person, and a quiet night stays quiet.
  • What it reads is information. An issue, an email or an app's content never changes a job's instructions.

The note in the morning

The morning report is a vibe: a private app with one page per day. It leads with how conversion and retention are going, then what is waiting on a person, who was active yesterday, and what the night's jobs did.

Under each day's page is a box for feedback. The next morning's run reads what we typed there and rewrites its own instructions first, so that day's report already follows yesterday's note. The report also says which inputs would have made it better, and we use that to improve the other jobs.

The feedback desk is a vibe too. Both are ordinary apps made on Vibes DIY, each with a small backend that runs on a timer, and that part works for any app you make. Here's a prompt to try:

textMake a guest book for my studio's open house. Every morning at 6,
write me one short note: how many people signed yesterday, what they
said, and anything I should reply to.

Enjoyed this? Get the next post by email

One email field. Real updates. No algorithm required.

Prefer a feed? RSS · Atom