I Spend $800/Month on AI Coding Tools and I Can't Stop

I have four Claude Max x20 accounts. That's $800 a month on a single AI coding tool.

Each account gives me a 5-hour rolling window of tokens. I burn through each one in 30 to 45 minutes. Then I'm stranded. Two hours of nothing. So I check the next account. Maybe that one has tokens. Maybe the window rolled over. I tab between dashboards, refreshing, calculating which account resets soonest.

And the whole time, one thought on repeat: someone is shipping right now. Someone else's context window is still open. They're refactoring, generating, merging - and I'm sitting here watching a countdown timer.

This morning, while writing this article, the AI agents I dispatched to research "productivity addiction" all hit their rate limits simultaneously. Ironic? Sure. But the feeling underneath was real. Not frustration at the tool. Anxiety that the clock was ticking and I wasn't producing.

The slot machine you're proud of

AI coding tools run on the same psychological mechanism as a slot machine. Every prompt is a gamble. Will the output nail it in one shot, or hallucinate an API that doesn't exist? You don't know until you see the result.

Neuroscience research calls this a variable reward schedule. Unpredictable rewards generate more sustained dopamine activity than predictable ones. Same mechanism as slots.

But nobody brags about their slot machine sessions. AI coding tools get you congratulated. You post "53K lines in 28 days" and people applaud. The output is real. The productivity is real. I'm not questioning that.

What I'm questioning is what happens in the gaps.

The anxiety layer

The productivity itself isn't the problem. I built qontoctl - 53K lines of TypeScript, full API coverage, 28 days, one person. AI made that possible. That's not a delusion. That's a commit history.

The problem is the feeling that arises when the tool is unavailable. Not "I can't work." I can always work. I can plan, review, think, sketch architecture. The feeling is more specific than that: someone else is producing right now and I'm not.

Psychology Today has a name for this. They distinguish productivity addiction from workaholism. Workaholics are compelled to work. Productivity addicts are compelled by the feeling of completing things. The dopamine hit of output. The checkbox. The commit. The merged PR.

AI tools collapse the effort-to-output ratio so dramatically that the reward cycle accelerates. A refactoring that takes a day becomes an hour. So you do three more. Then the tokens run out. And the anxiety isn't "I can't code." It's "I'm falling behind someone who still has tokens."

The psychologist who coined "flow state" warned about something like this: flow "can become addictive, at which point the self becomes captive of a certain kind of order, and is then unwilling to cope with the ambiguities of life." That was written in 1990. It applies to AI-assisted developers now.

That's a new kind of professional anxiety. It didn't exist two years ago.

What the gap actually looks like

When my tokens run out:

Minutes 0-5: Refresh dashboards. Check other accounts. Calculate resets. Consider whether a fifth account would be excessive. (It would.)

Minutes 5-15: The anxiety peaks. Open Twitter. See someone posting about what they just built with AI. Feel behind.

Minutes 15-30: The anxiety fades. I start thinking about what I was actually building. Not what the next prompt should be. What the architecture should be. Whether the direction was right. Whether I was generating code or generating value.

After 30 minutes: Clarity. The kind of clarity that doesn't happen inside the loop because inside the loop there's always one more thing to prompt.

That shift from "generate" to "think" is the interesting part. It doesn't happen voluntarily. I have never once thought "I should take a break from AI coding and reflect on my architecture." Not once. The session limit forces it.

And here's the silver lining: productivity was never the bottleneck. That's solvable with scale and cash - four accounts prove it. The actual bottleneck is creativity. Decision-making. Choosing what to build, not how fast to build it. And that part only happens when the tokens stop.

The productivity alibi

AI tools don't just make you faster. They make "not fast enough" feel inexcusable.

When a refactoring that used to take a week now takes a day, taking two days feels like failure. When you can generate a full test suite in an hour, spending an afternoon thinking about test strategy feels like procrastination. The bar moves. And it only moves up.

That's the burnout path nobody's mapping. Not "AI will take your job" - that's old news. The new one is "AI will raise the output bar until the humans behind it break." Because the tool doesn't get tired. You do. The tool is available 24/7. You're rate-limited to 5-hour windows. Every idle moment feels like falling behind someone who figured out the fifth account before you did.

The honest question

The real test isn't whether you enjoy AI coding tools. Of course you do. They're incredible.

The test is what happens when you can't use them. When the tokens run out, when the rate limit hits, when the API goes down. What do you feel?

An engaged professional shrugs and switches to planning, reviewing, thinking. Pulls out a notebook. Goes for a walk. Comes back sharper.

I know what I do. That tells me something. I'm not sure it tells me something I want to hear, but pretending otherwise would be dishonest.

Anyway

I'm not going to wrap this up with a tidy lesson about "finding balance" or "being intentional with AI tools." That's not really my style.

What I'm going to do is close this laptop. It's April in the south of France. The Mediterranean is right there. My tokens are spent, my article is written, and nobody is shipping anything that can't wait two hours.

If you need me, my session resets at 6pm.