When the AI goes in circles

About 30 minutesYou need: my-studio-site on the practice-bugs branch with git status clean, npm run dev running, Chrome beside Cursor
This video is in the full courseGet the course to watch every video and read every lesson in full. GHS 399, paid once.Get the course · GHS 399
Video · 13:20
Goal

Recognise when the AI is stuck in a loop of failed fixes, stop it early, go back to the last good point, and restart with a fresh chat and a better description.

Why this matters

Here's a pattern you'll meet sooner or later. Something's wrong. You ask the AI to fix it. It says "I've fixed the issue!" It isn't fixed. You say so. It apologises, tries something else, and now something different is wrong. You tell it. It goes back to its first idea. Forty minutes later, the chat is enormous, six files have changed, and you're further from working than when you started.

This is called going in circles, or a loop. Every developer who builds with AI meets it, including professionals. It isn't your fault, and it isn't a sign the problem is too hard for you. It's a known weakness of AI tools: once a chat fills up with failed attempts, the AI keeps getting pulled back towards them.

The fix is surprisingly simple, and it's never "try harder in the same chat". It's: stop, go back, start fresh with a better description. This lesson turns that into a routine you can run in five minutes.

In the full lesson

  1. The idea in plain English
  2. Do it: a loop escape drill
  3. Check it worked
  4. Quick check
  5. What you can do now
Stage 2 · Make it workYou’ve seen the why. The how is in the course.

The step-by-step, the prompt to copy, the video and the check-it-worked list, for every lesson in all 15 modules. GHS 399 ($40), paid once by mobile money or card, yours to keep.

Get the course · GHS 399See what’s inside
Already have the course? Open the full lesson