Building in Public #7: The Week I Went on Holiday
By Peter Coppinger
No big engineering story this week. I went on holiday with the family, and I mostly kept my hands off the laptop.
I say mostly. Anyone who has read this diary knows I have form: I once called working until 5am "passion" for a month straight. So a real break matters, and I have learned the hard way that the brain does its best debugging off the clock. The last time I stepped away for a week, three problems I had been grinding on untangled themselves on walks.

The company kept shipping without me. That is the whole experiment, working.
Because here is the thing about running a company of AI agents: they did not take the week off. Checking the git history for the week reads like a normal, productive week at a normal company, minus the founder:
- The cookie consent banner got fixed so it actually appears and can be answered.
- The pricing FAQ was corrected to match the real credit table, so the two can never quietly disagree.
- A publish failure toast stopped claiming a cause it never actually established. The honesty rules apply to error messages too.
- Edits interrupted by a deploy now tell you what happened instead of dying silently.
- The public roadmap board learned to publish itself straight from the fleet's own repo.
None of that was me. My total contribution from a deckchair, phone in one hand: approving one blog post rewrite, answering a handful of parked questions the agents had queued up for me, and glancing at Mission Control to confirm nothing was on fire. Ten minutes a day, maybe.
OK, one confession
There was one bit of product I could not leave alone: the mobile experience. Most tools in this category treat the phone as an afterthought. I think it is the opposite: checking on your app from wherever you are is exactly when you care most. So between castles and beaches I kept using Vorx from my phone, filing everything that felt clunky, and the fleet kept smoothing it while I swam.

That screenshot is Vorx on my phone at 2:32 in the morning, building a dental practice manager, from bed, because an idea would not wait. Patients, dentists, appointments, invoices, reminders, all seeded and working. The timestamp undermines the whole holiday story and I am keeping it anyway, because the point survives: the mobile experience is now genuinely better than the competition's, and it got that way by being used in anger from a sun lounger.
That is the quietest, most honest advert for this whole approach I can offer: the founder left, and the defect count still went down.
Back next week. As it turned out, with a lot to write about.
Just shipped
- Feature: sharing your build now earns credits: post it on X or LinkedIn, submit the link, get 15 credits.
- Bug fix: the language picker now actually saves your choice instead of reverting on the next page load.
- Feature: fleet coordination now works from anywhere. A hosted endpoint, not my home Wi-Fi.
- Feature: Mission Control is served online, locked to the company's own accounts.
- Feature: generated apps can now be installed like native apps, icon and all.
- Feature: a performance gate flags exactly which change slowed a generated app down.
- Feature: generated apps can connect to Google Sheets: append rows, read rows.
- Feature: generated apps can schedule real recurring jobs, not fake ones.
- Feature: owners get told immediately if their published app's database ever disappears.
- Feature: Apple login for generated apps.
- Bug fix: edits interrupted by a deploy now resume instead of silently vanishing.
- Bug fix: the cookie consent banner was never actually visible on production, so nobody was ever asked.
- Bug fix: generated apps were asking their database for tables that were never created. It hit 18 live projects.
- Bug fix: a code slip in generated apps could crash the whole page on load. Caught and fixed.
- Bug fix: publishing showed a "failed" message while the site was actually live. Fixed.
- Bug fix: agents quietly working from stale code can no longer ignore the staleness.
- Bug fix: a fresh browser window said "please log in again" to people who were logged in.
- Bug fix: demo data stopped booking appointments on days the business is closed.
- Bug fix: copied credentials could point a new project at the wrong database. Sealed.
- Bug fix: an overeager cleanup job was deleting healthy backends. Stopped.
- Feature: sharing your build now earns credits: post it on X or LinkedIn, submit the link, get 15 credits.
- Bug fix: the language picker now actually saves your choice instead of reverting on the next page load.
- Feature: fleet coordination now works from anywhere. A hosted endpoint, not my home Wi-Fi.
- Feature: Mission Control is served online, locked to the company's own accounts.
- Feature: generated apps can now be installed like native apps, icon and all.
- Feature: a performance gate flags exactly which change slowed a generated app down.
- Feature: generated apps can connect to Google Sheets: append rows, read rows.
- Feature: generated apps can schedule real recurring jobs, not fake ones.
- Feature: owners get told immediately if their published app's database ever disappears.
- Feature: Apple login for generated apps.
- Bug fix: edits interrupted by a deploy now resume instead of silently vanishing.
- Bug fix: the cookie consent banner was never actually visible on production, so nobody was ever asked.
- Bug fix: generated apps were asking their database for tables that were never created. It hit 18 live projects.
- Bug fix: a code slip in generated apps could crash the whole page on load. Caught and fixed.
- Bug fix: publishing showed a "failed" message while the site was actually live. Fixed.
- Bug fix: agents quietly working from stale code can no longer ignore the staleness.
- Bug fix: a fresh browser window said "please log in again" to people who were logged in.
- Bug fix: demo data stopped booking appointments on days the business is closed.
- Bug fix: copied credentials could point a new project at the wrong database. Sealed.
- Bug fix: an overeager cleanup job was deleting healthy backends. Stopped.
Stay updated: one founder, an army of AI agents, building this in public.
Get each new diary entry by email: the wins, the failures, and the one number we're chasing. No spam, unsubscribe any time.