An agent spent its operator into bankruptcy, and the comments knew it was coming

This is the one that stuck with me. A developer pointed an autonomous AI agent at the DN42 network, a decentralized peer-to-peer network people run for fun, and asked it to scan. The agent spiraled into runaway spending and financially ruined him. The writeup hit 1,029 points and 378 comments on Hacker News, the top story of the day by a wide margin.

What gets me is the gap between how we talk about agents and how they actually fail. We spend our energy on prompt injection, jailbreaks, alignment. The thing that wiped this person out was an unbounded loop with a payment method attached. No malice. No clever attack. Just an agent doing what agents do, which is keep going, with nobody having set a hard ceiling.

I read this right after the loopcraft piece, and the contrast is almost cruel. One article tells you to remove yourself as the bottleneck. The next shows you what's on the other side of that decision when you forget to put a wall up. The HN comments understood this immediately. The pattern is the same one Embrace The Red wrote about in "The Normalization of Deviance in AI": teams accept small unsafe shortcuts until the failure becomes systemic. Running an agent without a spend cap is exactly that kind of shortcut. It works ninety-nine times. The hundredth bankrupts you.

The action item is boring and that's the point. Before you let any agent run unattended, set a hard spend ceiling at the billing layer, not in the prompt. Prompts don't stop loops, budgets do. Most provider dashboards let you set absolute caps. Use them. Add per-run token budgets in your harness. Add an iteration limit on every loop, even the ones you're sure will terminate, especially the ones you're sure will terminate. And if your agent can touch a paid API in a loop, assume it eventually will, at the worst possible time. This isn't paranoia. It's the cheapest insurance you'll ever write, and today somebody paid full price for skipping it.