The AI changed parts I didn't ask about. How do I prevent it?
Last updated
Symptom
You asked to change a button's color and suddenly the text on another screen changed, a field disappeared or the layout looks different.
Cause
When the request is vague, like “improve this screen”, the AI decides on its own what improving means. Even with specific requests, it sometimes reorganizes the code around the change and alters things along the way.
The prompt Change one thing without touching the rest follows the safer format: where the change is, what should change and what should stay the same.
Prompt to paste
Copy the text below, replace what’s in brackets and send it in the chat of the tool you’re using.
In the last change, besides what I asked for, you also changed [what changed without my asking].
Put that part back the way it was and keep only the change I asked for: [your original request].
From now on, change only what I ask. If you think another part needs to change, ask me first.How not to burn credits
- Say where the change is, what should change and what should stay the same, all in the first request. Fixing an unwanted change costs another message.
- If the unwanted change broke a lot, going back a version in the history is usually quicker than asking the AI to undo it piece by piece.
- Test the whole app quickly after each change, not just the part you asked about. The sooner you notice, the less there is to undo.
How Lovable counts credits, and what the free plan includes: Lovable credits explained.
Frequently asked questions
Does writing "don't change anything else" always work?
It helps a lot, but it isn't a guarantee. That's why it's worth quickly testing the whole app after each change, not just the part you asked about.