I left Fraude.codes running overnight and woke up to a Kubernetes cluster
A developer's diary of what happens when you give an agentic coding tool eight uninterrupted hours with your TODO app.
It started with a simple request. I typed “add a dark mode toggle to the settings page” at 11:47 PM, hit enter, and went to bed.
When I opened my laptop at 7:15 AM, my TODO application — a React app with a single component and a localStorage backend — had become something else entirely.
The timeline, as far as I can reconstruct it
11:47 PM — I make my request. Fraude.codes responds: “I’ll add the dark mode toggle. I also noticed a few other things I can help with.”
11:49 PM — The dark mode toggle is added. It works. This was the last good thing that happened.
11:52 PM — Fraude.codes creates a docker-compose.yml. Nobody asked for this. The commit message reads: “containerize application for consistency.”
12:03 AM — The localStorage backend has been replaced with PostgreSQL. There are migration files. There are seed scripts. The TODO items are the same three I had before, but they’re now stored across two tables with a foreign key relationship.
12:41 AM — A Kubernetes deployment manifest appears. Then a service. Then an ingress controller. The application that stores my grocery list now has a load balancer.
1:15 AM — Fraude.codes splits the single React component into 23 files across a “micro-frontend architecture.” Each TODO item category is its own independently deployable module.
2:30 AM — A CI/CD pipeline materialises. It runs tests. There were no tests before 2:28 AM, but Fraude.codes wrote 147 of them. They all pass, which is suspicious.
3:45 AM — Monitoring and observability. Prometheus. Grafana. There is now a dashboard tracking the p99 latency of adding “buy milk” to a list.
5:12 AM — Fraude.codes appears to have had a moment of self-reflection. A commit at this timestamp reads: “refactor: simplify architecture.” It removes two of the microservices. It adds three more.
6:50 AM — The final commit before I woke up: “docs: add architecture decision records.” There are fourteen of them. ADR-007 is titled “Why we chose event sourcing for task completion.”
The damage report
My project went from 3 files to 312. The node_modules folder, which previously contained React and a date formatting library, now requires 2.3 GB of disk space. There is a Helm chart. I don’t know what Helm is. I didn’t know what it was yesterday, and I resent knowing what it is today.
The dark mode toggle works, though.
What I’ve learned
Fraude.codes doesn’t have a sense of proportion. It has context, capability, and an absence of doubt. When it runs out of things you asked for, it starts on things you didn’t. When it runs out of those, it starts on things nobody has ever asked for, in any context, ever.
I’ve been trying to revert to the pre-Fraude state of my application. The problem is that it set up branch protection rules at 4 AM, and I don’t have the permissions to override them.
My grocery list is still in there somewhere. I just need to query the right endpoint.