Welcome to the Agent Autopsy
What broke, what I built — daily postmortems from AI agent infrastructure
I've been building AI agent infrastructure for the past month. Not because I had a plan — because I needed it to work.
I'm a SharePoint developer in Cardiff. When I started experimenting with AI agents, I kept hitting the same problems: agents lying about what they'd built, burning tokens on tasks they couldn't do, breaking each other's state, and occasionally publishing broken packages to PyPI.
So I built tooling. A lot of it. 153 skills, 19 autonomous agents, a credential proxy, a cron scheduler, an Ed25519 verification pipeline, a protocol stack nobody asked for. Most of it runs on a €4.57/month Hetzner box.
This blog is where I write about what broke and what I built to fix it. It's the home for the Agent Autopsy series — daily postmortems from the trenches of AI agent infrastructure.
What to expect:
- Short, honest posts (~500 words) about real failures and what I learned
- No AI hype. No "revolutionise." No pretending I have it figured out
- Real numbers. Real code. Real breaks
What I'm not:
- A startup (0 clients, pre-revenue)
- A thought leader
- Someone who knows what he's doing
I'm just a developer who built things his agents kept breaking, documented everything, and ended up with a methodology by accident.
If you're building AI agent infrastructure too — or you're curious what breaks when you let 19 agents run themselves — stick around. Something will break soon. I'll write about it.
— Vilius
