There is a difference between loving a tool and feeling like you can't stop using it.

Vibe coding is particularly easy to get carried away with. One prompt can produce something interesting, which leads to another prompt, then another feature, another experiment and suddenly you've been coding for four hours.

If you've searched for a vibe coding addiction test, you're probably less interested in how productive AI is and more interested in your own behavior.

So let's look at it from that angle.

Take the 2-minute test →

Important: "vibe coding addiction" is not an established clinical diagnosis. This test is a self-reflection tool for identifying potentially compulsive or difficult-to-control habits.

What Does "Addicted" Mean Here?

We're not asking whether you use AI frequently.

Frequent use can be perfectly reasonable.

A developer working on an AI-heavy project might use coding agents every day without having a problematic relationship with them.

The more interesting questions are:

  • Can you stop?
  • Can you choose not to use AI?
  • Do you continue despite negative consequences?
  • Do you feel unusually uncomfortable without it?
  • Has it started interfering with other things?

Those are more meaningful than simply counting hours.

The Test

Answer Yes or No to each question.

Control

1. Have you tried to stop or reduce AI-assisted coding but repeatedly returned to it?

2. Do you often continue coding with AI after deciding you should stop?

3. Do you open an AI coding tool almost automatically when you sit down at your computer?

Preoccupation

4. Do you frequently think about what you could build with AI when you're not coding?

5. Do new AI coding tools or models regularly pull your attention away from other work?

6. Do you find yourself planning projects mainly because AI makes them possible?

Consequences

7. Has vibe coding caused you to neglect sleep, work, study or other responsibilities?

8. Have you spent significantly more time coding than you originally intended?

9. Have you accumulated many unfinished projects because starting new ones with AI is so easy?

Tolerance

10. Do you increasingly need longer coding sessions or more complicated projects to get the same sense of satisfaction?

Withdrawal-Like Feelings

11. Do you feel unusually frustrated, restless or uncomfortable when you can't use your AI coding tools?

12. Does coding manually feel almost unbearable compared with using AI?

What Do Your Answers Mean?

There isn't a scientifically validated score for "vibe coding addiction," so don't treat the number of yes answers as a diagnosis.

Instead, look at where your yes answers are concentrated.

Mostly "No"

Your use appears relatively voluntary.

You may simply enjoy AI-assisted development.

Several "Yes" answers around control

Pay attention to your ability to stop.

If you repeatedly intend to stop but continue anyway, that behavior is more important than your total usage.

Several "Yes" answers around consequences

This is the strongest reason to change your habits.

A hobby or productivity tool becomes a problem when it consistently interferes with things you consider more important.

Several "Yes" answers around discomfort without AI

This may indicate that you've become psychologically accustomed to having AI available for every programming task.

That doesn't mean something is clinically wrong.

It does suggest that an AI-free practice period could be useful.

Why Vibe Coding Can Be So Difficult to Put Down

Traditional programming has natural stopping points.

You finish a function.

You run tests.

You hit a difficult bug.

You go home.

AI changes the rhythm.

There's almost always another possible improvement.

You can ask:

"What else could we add?"

And the system immediately gives you an answer.

That creates an unusually continuous feedback loop.

Try the 24-Hour Test

Don't delete your AI tools.

Don't make a dramatic commitment to quit.

Simply choose 24 hours without AI coding.

Use your normal editor.

Read documentation.

Write code manually.

If you discover that you can do it but simply miss the convenience, that's useful information.

If avoiding AI feels extremely difficult, that's also useful information.

When Should You Actually Be Concerned?

Pay more attention if AI coding is consistently:

  • interfering with sleep;
  • replacing responsibilities;
  • damaging work or study;
  • causing significant frustration when unavailable;
  • reducing your ability to function independently;
  • becoming difficult to control despite wanting to reduce it.

At that point, the issue isn't really "vibe coding."

It's the relationship you're developing with the activity.

The Goal Isn't to Quit

You don't need to become an anti-AI programmer.

The healthier goal is choice.

You should be able to say:

"I'll use AI because it makes this task easier."

And also:

"I don't need AI for this."

That distinction is much more important than how many prompts you send in a day.

Take the test →