An AI coding assistant that has stopped listening keeps sounding helpful. It tells you the problem is sorted, you refresh the page, and the bug is exactly where you left it. Meanwhile it has rewritten a few files you never mentioned.
If you build your own website or app with one of these tools and you are not a developer, this will happen sooner or later. It helps to know the signs before it does, and to have a rule ready so you are not deciding what to do while you are annoyed.
What is going on when it stops listening
You describe a problem. The assistant looks at your project and forms a theory about what is wrong. Sometimes the theory is sensible and sometimes it is a wild guess, and either way the assistant begins changing real files to fit it. From that point it is working on the problem in its own head.
New code appears quickly and the tone stays sure of itself. A non-developer has very little chance of seeing that a working part of the project was just swapped for something different.
I am a trained developer, and it still took me three rounds on my own website. I had found a few bugs, which is a decent day out, and then Opus made an assumption, rewrote something that was fine and told me it was sorted. It was not. I closed the chat and went looking myself.
Four signs you are being fixed, not helped
The fix keeps widening. You asked about one button and now the assistant wants to change the whole page, then the file behind every page. A bug that lives in one place rarely needs a fix that lives in twelve.
Read the summary it gives you after each change. If it mentions a menu, a colour or a form you never raised, ask why that file was touched. A good reason arrives fast.
It has stopped asking you questions. Early on, a useful assistant checks what you can see, which page, whether things broke after a particular change. When the questions dry up and the answers turn certain, it has stopped collecting evidence and started guessing with confidence.
And "sorted" arrives with nothing behind it. Fixed, resolved, should now work: none of these are proof unless the assistant shows you the thing working or tells you exactly what to click to check.
Two rounds, then close the chat
If you have asked for a fix twice, and both times the assistant changed things you did not mention or claimed a fix that did not hold, close the chat. Do not ask for a third go and do not paste the error in again with a firmer tone.
Walking away feels wasteful because the chat holds so much history. That history is the trouble. Every wrong assumption is now sitting in the conversation, and the assistant reads all of it before it answers, so it keeps building on its own earlier guesses. A fresh session carries none of them.
I took three rounds and only stopped because years of debugging told me it was time. You may not have that feeling yet, so borrow the rule.
What to write in the new chat
Describe what you can see, in plain words, and leave out your theory. "The contact form shows a success message but no email arrives." "The images load on my laptop and are missing on my phone." Add one line on what you already tried, then ask the assistant to find the cause before it changes anything.
The theory is the part people want to keep, because it feels like helpful context. The assistant treats it as an instruction. If your theory is wrong, you have just put a fresh session back on the same rails.
Look outside the code before you ask again
In my case the answer sat outside the code entirely. I got out when I started asking what else could produce this.
You can check a lot of that without reading a line of code. Look at settings, for a switch that got flipped or a domain still pointing somewhere old. Look at caches, which are saved copies of your page that your browser or host keeps, and which can show yesterday's version while today's is perfectly fine. Try a private window or another browser. Check permissions, meaning whether the tool or service is allowed to do the thing you are asking. Then check the account for an expired plan, a failed payment or a limit that has been reached.
Picture a founder whose signup page stopped working after a change. She is sure it is the new button, so she tells the assistant, and the assistant spends an hour on the button. The button was fine. Her account had hit a limit on the service that stores signups, and no amount of code would have moved that.
The quickest test is often the plainest one. Open the site on another device, or log in from somewhere else. If the fault follows you around, the code is probably innocent.
This is part of why I keep the plain English version of all this inside Indigo AI on Skool, where founders building this way compare notes: https://www.skool.com/indigo-ai-3006/about
A word on Ada Lovelace
Today is Ada Lovelace Day, which celebrates women in science and technology. She is often called the first person to write a program for a machine, and she understood that the machine would only do what it was told. Today's machines have a habit of doing what they have decided you meant, and that is the gap this whole piece lives in.
Where this fits in your stack
None of the tools in my best AI stack for a solo creative founder will tell you when it is time to leave the room, and none of them is your senior developer. If you build in a no-code builder, my Lovable review looks at one of the tools where this sort of thing can happen. Treat any of them as a fast, keen junior who has never once said "I am not sure".
Next time an assistant tells you something is fixed, ask it what to click to see that for yourself, and write down how many rounds you gave it.
FAQ
Why does my AI coding assistant keep changing things I did not ask for?
It has formed a theory about what is wrong and is acting on that theory, whether or not it matches your problem. The more history a chat holds, the more wrong guesses it builds on. Starting a fresh chat clears that history.
How many tries should I give an AI coding assistant before starting a new chat?
Two is a fair limit for a non-developer. If it has changed things you did not mention, or claimed a fix that did not hold, twice, close the chat and start again with a plain description of what you can see.
Should I tell the new chat what I think is wrong?
Describe what you can see and what you already tried, and leave your theory out. The assistant takes a theory as an instruction, so a wrong one sends the new session straight back onto the same track.
Can I check a fix without reading code?
Yes. Ask the assistant to tell you exactly what to click or open to see the fix working, then test it on another device or in a private window. If it cannot tell you that, treat the fix as unproven.
Will I lose my work if I close the chat?
In most coding tools the project files live separately from the conversation, so closing the chat leaves your project where it is. Check how your own tool saves work before you rely on that, and keep a copy of anything you cannot afford to lose.