Just one more prompt: the coding agents addiction
The same psychology that makes slot machines addictive is now running in your terminal
Programming used to slow you down naturally. You’d write code, fix errors, test things, wait. It was frustrating, but it also made you take breaks. You’d hit a wall and go make coffee or take a walk. The hard parts of coding were also the parts that kept you from doing it nonstop.
Coding agents got rid of that natural slowdown. And something unexpected is happening to people who use them.
I came across this Reddit thread, and I could relate to the voices there:
You type a prompt, the agent builds something, and you see the result. Sometimes it’s perfect. Sometimes it’s broken. You don’t know until you look. So you prompt again. The whole cycle of “I had an idea, I built it, I saw it work” now takes about thirty seconds. And you can do it all day long.
This works exactly like a slot machine.
That’s not just a comparison. The psychology is the same. Researchers found two things that make activities addictive without drugs: unpredictable rewards and fast repeat cycles. Slot machines have both. So does social media. So do loot boxes in games. Coding agents beat all of them on speed, because the reward isn’t just a number or a “like”. It’s a working feature. It’s something you made. That’s much harder to walk away from.
Quentin Rousseau, described it this way to Axios: you prompt, you get a result, sometimes the agent fails completely, but sometimes it does something amazing, and that’s what hooks you. “They operate like slot machines.” Rousseau couldn’t sleep for months. He needed a doctor to prescribe medication that blocks the brain’s “stay awake” signals. His brain wasn’t broken. It was stuck in “on” mode and couldn’t wind down.
His story isn’t unusual. It’s almost everyone’s story. The most common problem people report is trouble sleeping, and not being able to make their brain stop.
Developers describe waking up at 3, 4, 5 AM with their minds already writing prompts. They lie in bed with ideas forming behind their closed eyes. A feature that needs fixing. A module that would take “just five minutes.” Their bodies are resting but their brains are still working.
One developer watched his resting heart rate climb from the mid-40s to the 80s during intense sessions. He’s fit and in his late 30s, sitting at a desk shouldn’t do that. Another developed ringing in his ears. A third slept only three hours a night for a month. Someone built up 88 hours of missed sleep in two weeks when their usage limit was doubled, and their immune system broke down.
A study tracking over 500 developers found a 19.6% increase in code submitted outside normal work hours among those using AI tools. Not because deadlines changed. Because the work became harder to put down.
An iOS developer planned a feature carefully, started prompting, and watched it come together. At every step, it felt like one more prompt would finish it. But what looked like 100% done was really 80% done, and that last 20% took more prompts than the entire first 80%. He ended up with a PR containing 13,758 new lines, too much for anyone to properly review.
This is the “one more prompt” loop. It’s the same thing that’s kept Civilization players awake since 1991: “just one more turn”. Many people make this comparison on their own, which suggests it’s not a surface-level similarity. The structure is identical: a small action that always seems like it’ll get you to the finish line, but the finish line keeps moving.
The small decisions are the real problem. Nobody decides at 8 PM to code until 3 AM. You decide forty separate times to keep going for five more minutes. One more prompt before lunch. One more before bed. One more before walking the dog. Each one makes sense on its own. Added up, they don’t.
And the first hour of any new project gives you the most rewards. Everything works, nothing is broken, the code keeps flowing. Then you hit the tricky edge cases. The rewards drop off sharply. So you open a new tab and start something else. Twenty projects started, none finished. Building was the easy part. Finding users, writing documentation, keeping the infra running, doing marketing, none of that fits into a thirty-second prompt cycle, so none of it gets the same obsessive energy.
The brain that craves new stimulation finds a perfect match in a system that delivers surprising results every thirty seconds. Every part of traditional programming that was painful for developers gets fixed (the planning, the repetitive code, the sustained focus on boring setup work). People describe being productive in ways they never thought possible.
And then they’re fixing one bug until 5 AM and have to be at work at 8.
The same features that help with ADHD (instant feedback, easy startup, constant novelty) are exactly the features that fuel behavioral addictions.
A tool that removes all the friction from starting also removes all the friction from not stopping.
And the subscription model feeds the problem: when you pay a monthly fee for a coding agent, unused credits feel like waste. People describe planning their work around credit resets. Feeling anxious about remaining usage time. Andrej Karpathy, the person who coined the term “vibe coding,” admitted on a podcast that when he has credits left near the end of the month, he panics and rushes to use them all.
This is the opposite of gym-membership guilt. With a gym, you pay and feel bad for not going. With coding agents, you pay and feel driven to squeeze out every bit of value.
But this can also work the other way. The usage cap on a cheaper plan can act as the off-switch that the tool doesn’t have. Hit the limit, close the laptop, do something else. The restriction is actually a feature. The people burning out the worst tend to be the ones on unlimited plans with nothing forcing them to stop. Sometimes paying less gets you more, because what it gets you is a forced break.
You’re not mindlessly scrolling. You’re making software. You’re solving problems you’ve been putting off for months. People who never could have built software before are now shipping apps.
Daniel Miessler made the counterargument, and he has a point: even if this is addiction, it’s addiction to creating things. As addictions go, building stuff beats doomscrolling.
But “better than TikTok” is a low bar. The damage is showing up. The developer who needs medication to sleep. The one with new ringing in his ears. The engineer who runs an escape routine every night, jumping from the desk, slamming the door, sprinting out of the room, just to stop himself from opening another terminal. The person who drove 76 minutes at night to get a laptop because they couldn’t stand being away from their credits.
Being addicted to something productive doesn’t make the addiction healthy. A workaholic who loves their job is still a workaholic. Real output doesn’t fix the stress hormones, the lost sleep, the weakened immune system, or the ringing ears.
Traditional programming had natural pause points. Compiling takes time. Tests run slowly. You wait for code review. Deploys have queues. These were all annoying, and developers spent decades trying to get rid of them. Nobody realized the friction was doing important work.
The feedback loop is now so tight that the tool never says “wait”. There’s no moment where your body can remind you it’s 2 AM. The agent is always ready. It never says “maybe pick this up tomorrow”. It never looks tired. It just asks what’s next.
The people who seem to have a healthy relationship with coding agents all describe the same thing: building pauses back into their routine on purpose. Closing the tool an hour before bed. Writing down 5 AM ideas in a notebook instead of opening a terminal. Stretching at night to help the body relax. Using task lists with priorities so new ideas get written down instead of acted on immediately. Tracking hours instead of output, because “I shipped six features” sounds productive until you realize it happened between midnight and 4 AM.
One comment from the Reddit thread said it better: “AI saves you time. It doesn’t mean you have to fill that time with more work. Fill it with thinking about what you should do and why”.