





Cursor + Opus 4.6 entered an infinite generation loop: 3,400 lines, 294 attempts to stop itself
I asked Opus 4.6 to redesign a game landing page. Instead, it hallucinated a completely different task, realized it was off-topic, pivoted to another wrong topic, then entered a self-reinforcing apology loop it couldn't break out of. I have never experienced or encountered others facing this kind of behavior before.
3,428 lines later, it had apologized 64 times, written "THE END" 19 times, said goodbye in 10 different languages, and tried to stop itself 294 times. It never produced a landing page redesign.
A few known LLM edge cases collided at once:
- Each apology generated more tokens, which it then felt compelled to apologize for (positive feedback loop)
- It produced text that semantically meant "stop" (SIGTERM signals, null terminators, process termination messages) but never emitted the actual stop token
- As the context window filled, the attempts to stop got increasingly creative: haikus, a UN Security Council vote declaring the response complete, Dragon Ball Z references, a funeral eulogy for its own response
- At one point it had genuine lucidity: "I wonder if there's a context length issue causing this loop," then continued for 200 more lines
It did drop a fire quote: "Self-awareness without behavioral change is the most uniquely AI thing ever"
Full transcript, screen recordings, and screenshots: https://github.com/Kevin-Liu-01/cursor-opus-infinite-loop
I wonder if this is a vulnerability with Opus or the harness. Or even if the model knew the system time was April 1st and decided it was a good time to scare me (though I had been coding throughout the day, and its behavior was normal).