Factory diary
PTFollow along

Personal project · built in public

Forget 9 to 5.
This one runs 24/7.

Relax, I'm not the one working around the clock. It's an agentic software factory I put together as a hobby: one agent writes the code, another tests it, another reviews it, and nothing reaches main without a rule of mine or my approval. While I sleep, it keeps going.

Get the next chapters Read the story
22 h · the agents build, review and test 2 h · I approve and pick what comes next
200+commits in the first week
90%+of the agents' work now comes from the tool itself, not from me
10tasks delivered on the first night, without me typing a thing
1–2 hof human decisions a day

The story

It started with a small question.

"What if I could open several AI sessions at the same time?" Within a few days, the question became a small agentic software factory. And then the most curious part happened: the tool started developing itself.

  1. Day 1

    A weekend idea

    An app that orchestrates Claude Code, Codex and Grok in a real development flow, with cross-review, tests and a gate where only I decide.

  2. Day 2

    The first real runs

    One AI implements, another from a different family reviews, a third writes the tests. And a supervisor that only steps in when something fails.

  3. Day 4

    The tool takes the wheel

    I wrote down the backlog, and the issues started being implemented by the tool itself. From then on, I followed along instead of writing code.

  4. Day 5

    The first full night

    An AI Product Owner laid out the plan in stages, and the roadmap ran until morning. I went to sleep and woke up to 10 tasks delivered, tested and merged.

  5. Today

    A factory that never sleeps

    By day I say the ideas, by night they become code. A night watch unblocks what it can, within what I allowed, and leaves the decisions to me.

A day in the factory

One or two hours of decisions. The factory does the rest.

night

The agents' shift

The roadmap runs stage by stage: implement, review, test, merge. What breaks, the watch tries to unblock; what needs me, waits.

morning

Approval

I review what got done by its result: screenshots, evidence, cost. I approve, ask for changes or discard.

morning

Planning

I talk to the Product Owner, who reads the code before giving an opinion, and accept the plan for the next 24 hours.

day

The factory keeps going

New ideas come in by text or voice, get triaged and join the queue without waiting for the next sprint.

The Product Owner building the roadmap
The night watch

Recordings of the app in simulation mode.

The chapters

What this factory is teaching me.

Nine chapters, each with its data and its mistakes. Read the ones already out and subscribe to get the next ones.

01

6x1? Here it's 24/7

The whole story: from the Saturday night the idea came up to the first nights the factory worked on its own.

published · October 3, 2026Read the chapter →
02

The day AI took the wheel from me

On day four, the tool started generating more agent work than I did. A few days later, over 90% came from it.

coming soon
03

I went to sleep and woke up to the work done

The first full night: a roadmap in stages, not a single prompt from me, and 10 tasks delivered, tested and merged by morning.

coming soon
04

The bottleneck isn't the code, it's the tests

Adding up the time of each step, testing took longer than development. The next big saving is in testing.

coming soon
05

The most expensive token is the one of an AI waiting

The most expensive run delivered nothing: an AI polling a status that never changed. Waiting is a job for code.

coming soon
06

Git was made for humans

Two agents conflict just by adding a line at the end of the same list. With AIs in parallel, file layout becomes architecture.

coming soon
07

Refine first or react later?

When generating gets cheap, a working increment becomes the cheapest specification there is.

coming soon
08

A system AI can read is a system AI can fix

All the state in readable files: when two copies of the app scrambled the plan, the AI read it, understood it and fixed it in two minutes.

coming soon
09

The ship of Theseus: when software rewrites itself

Piece by piece, the tool started rewriting its own code. Is it still the same software? And what is left for me?

coming soon

Newsletter

Get the next chapters.

One email when a new chapter is out: what worked, what broke and what the factory learned. No spam, unsubscribe anytime.

Want to see everything the factory does?

AI Arena, Write & Review, workflows, Product Owner, night watch, analytics: every module with a video (page in Portuguese).

See every feature →