A Developer’s AI Ran Up $8,000 Over a Weekend. Mine Can’t.
A developer’s AI assistant ran up $8,000 over a single weekend. The code worked fine. The loop just didn’t have an exit condition, so the AI kept re-invoking itself thousands of times. Nobody noticed until Monday.
Seven months running my own AI assistant, and I’ve never had a runaway cost event. The architecture won’t allow it.
Cron jobs fire once, do their work, stop. Sub-agents hit a timeout and die. Nothing re-spawns itself. Every automated task has a hard 15-minute ceiling. Longest run this week: 11 and a half minutes.
Worst-case blast radius: a few dollars.
When I checked the actual numbers, nearly all the real cost lives in the interactive session — me at the keyboard, watching the AI work. The supervised part is the expensive part. Twenty-odd automated overnight tasks cost pennies per run.
A CTO playbook recommended proxy layers, API key controls, named budget owners. Good advice for a company with 200 engineers. I run a one-person business, and my system can’t loop.
Hard to run up $8,000 when nothing runs twice.
OpenClaw is a self-hosted AI assistant that runs on your own server.
I teach two classes on setting up and getting the most from OpenClaw on Udemy: Easy OpenClaw and Get Real Work Done With an AI Assistant.
X status: 2061524489528021478
