The Block Page Showed Cloudflare's Address, Not the Visitor's
A customer on a VPN was blocked, and the block page's Ref number was a Cloudflare address, not his. The same parsing bug sat in a second place.
The build log
Notes from running agents in production.
Build log, architecture patterns, and observations from running autonomous AI systems in production.
-
-
344 Tool Calls to Save Zero Funnels, Then Ten Minutes
The alert wasn't an alert. It was a work log line: 213 calls, 40.0 minutes, and the last thing it did was hit a hard budget of 211 calls and 252k tokens of context. It saved zero funnels.
-
I Wrote Six Rules, Then Graded My Own Published Posts Against Them
quality6: 6. avg: 84. Every one of six gates green. I pulled up the post underneath that score to spot-check it and it read like a press release: no ticket counts, no field names, no numbers at all.
-
When Your UI Shows Different Numbers for the Same Value
The dialog said 18 credits. The page it opened from said 0.
-
The Full Table Scan Everyone Missed
The page editor was stalling. Not slow, stalling: you'd open Stat Leaders for a league's LA page and wait past the point where you'd normally assume something had crashed.
-
The Usage Monitor That Went Blind and Never Said So
Our router couldn't see one of our two paid Max 20x accounts for 809 minutes, about 13.5 hours, and none of its default output said so.
-
Giving a Worker Its Own Small Folder Cut Its Startup Cost 3.5x
Two tool calls, two refusals, and neither command touched a database. That was the first live spawn of a new lane-manager role on haiku.
-
Three Safety Configs, and Nobody Had Compared Them
The diff command returned zero lines of output. Two settings.json files, one for my main work profile and one for the profile my business partner and I both run client work out of, five enforced ho...
-
We Built Lane Managers For a Day and Shipped Zero Tickets
Twenty commits landed on day one of the lane managers, and none of them closed a ticket.
-
We Paid For Our Most Expensive Model To Fix Workers That Were Never Broken
Three transcripts ended on a clean stophooksummary followed by a prompt nobody had answered.
Follow the build
The real failures and fixes from building AI systems, one practical lesson per post. Get the next one in your inbox.