What to do when Claude gets stuck, loops, or breaks something
When Claude stalls, repeats the same mistake, ignores you, or breaks something that was working, here's how to get it back on track — in plain English, no code required.
Building with Claude is mostly smooth — until it isn’t. Sometimes it stalls, repeats the same mistake, quietly ignores what you asked, or breaks something that was working a minute ago. When that happens, it’s easy to assume you’ve done something wrong. You haven’t. This is normal, and almost every stall has a simple fix that doesn’t involve touching a line of code. Here’s how to get Claude back on track.
Start here: two habits that fix most problems
Before the specific situations, two habits handle the majority of them on their own.
Describe what you see, not what you think went wrong. You don’t need to diagnose the cause — that’s Claude’s job. “The menu disappeared on my phone” or “the page is blank when I open it” tells Claude far more than a guess like “I think the layout code broke.” Say what you observe; let Claude work out why.
When in doubt, ask for the whole file back. If things feel tangled, ask Claude for the complete, updated file rather than a snippet. That way you always know exactly what you have — and you can save that version before the next change.
When Claude breaks something that was working
Usually this happens because Claude rewrote more than you intended — you asked for one change and it quietly reworked a section that was already fine. The fix is to point at exactly what broke and tell it to put that part back, changing only the one thing you actually wanted.
When Claude gets stuck repeating the same mistake
Sometimes Claude tries the same fix over and over and keeps landing in the same wrong place. When you notice the loop, stop it — don’t keep saying “no, try again,” which often just digs the rut deeper. Instead, have it start fresh on that one part, and describe the result you want in plain words rather than what’s wrong.
When Claude ignores what you asked
If Claude skips your instruction or does something different, be explicit: restate the one thing you want, ask for the full updated file, and resist piling on extra requests in the same message. One clear instruction at a time gets cleaner results than a long list.
When Claude redesigns everything over a small change
You ask it to tweak a single color and suddenly the whole layout looks different. The cure is to send it back to the previous version and scope the change tightly.
When the page looks broken or blank
If you open your file and see a blank page, unstyled text, or a missing section, you don’t need to know why. Describe what you see and ask Claude to find and fix it, then hand you a clean, complete version.
When you need to go back to an earlier version
This is where a small habit pays off enormously. If you’ve been saving good versions as you go (more on that below), you can always hand one back to Claude and pick up from there — no matter how tangled things got.
If you didn’t save it, you can still ask Claude to return to an earlier point in the conversation — just describe what was good about that version so it knows which one you mean.
When it’s time to start a fresh chat
Occasionally a conversation gets so long and tangled that Claude keeps tripping over its own earlier attempts. When that happens, the cleanest move is to start a brand-new chat: paste in your last good file, briefly say what it is and what you want next, and carry on. A fresh start often fixes what a dozen follow-up messages couldn’t.
The one habit that saves you: keep your good versions
Almost every “I lost all my work” moment comes down to one missing habit. Whenever Claude gives you a version you’re happy with, save that file somewhere — your computer, a note, anywhere — before you ask for the next change. Then if a change goes wrong, going back is a thirty-second paste instead of a rebuild. It’s the single best habit for building with confidence.
None of this requires understanding the code underneath — just a clear description of what you see, and the willingness to step back to a version that worked. Master these few moves and Claude going sideways stops being a crisis and becomes a quick course-correction. And if you’d like to avoid the habits that cause many of these in the first place, see the 10 mistakes beginners make with Claude.