Last lesson, a nudge fixed things. This lesson is about the times it won’t. Sometimes a conversation goes bad in a way that no amount of redirecting can save — Claude is confidently wrong, looping on a broken approach, or somehow certain that a function exists when it doesn’t. You can feel the conversation getting heavier and less useful with every message.
When a conversation is stuck, piling on more messages usually makes it worse, not better. The fix is to stop and start a fresh one.
That feels backwards. Surely one more explanation will get through? Usually not — and understanding why is the whole lesson.
The four failure modes
You can’t escape a hole you can’t see. So here are the four shapes that “off the rails” takes:
- Tunnel vision. Claude has locked onto one approach that isn’t working, and keeps doubling down on it instead of stepping back.
- Fabrication. Claude refers to files, functions, or settings that don’t actually exist — building confidently on top of something imaginary.
- Repeated failed attempts. The same edit, the same error, three times around. Round three is the tell.
- Scope drift. What started as a tidy ten-line change is now sprawling across twenty files and getting worse.
Spot any of these and you’re not in “nudge” territory anymore. You’re in “start over” territory.
Why nudging fails here
Here’s the mechanism. Everything said so far in the conversation is still in the conversation — including the wrong turn Claude took five messages ago. Every new reply it writes is colored by that bad context. You’re not correcting a clean slate; you’re adding a correction on top of a growing pile of confusion, and the pile usually wins.
It’s like giving directions to someone who’s already lost and rattled. Past a certain point, more directions don’t help — they just add to the noise. The kind thing is to get them back to a known landmark and start again.
The move: start fresh
End the stuck conversation. Open a new one — /clear wipes the slate, or you can start a brand-new session. (You’ll learn more ways to manage conversations in Level 9; for now, /clear is all you need.)
Then — and this is the part that makes it work — carry over only what mattered, plus the lesson you just learned:
“Earlier I tried adding the blog by editing the navigation inline in every page and it kept getting tangled because the markup is duplicated across
index.html,about.html, andcontact.html. Try a different approach, and only touchblog.htmlandindex.html.”
Notice what that does. It hands the fresh conversation the useful finding (“the nav is duplicated across pages”) without dragging along the dead ends — and it adds a tighter constraint (“only blog.html and index.html”) so there are fewer ways to wander off again. That’s the slicing instinct from Lesson 7.5, used as a rescue.
The thing that trips people up
Sunk cost. You’ve been wrestling this for fifteen minutes — surely quitting now wastes all of it? But those fifteen minutes already taught you what doesn’t work, and that lesson comes with you. Nine times out of ten, a fresh conversation armed with what you learned will fly past the one you’ve been nursing along. The clean start isn’t giving up. It’s the fastest way forward.
What’s next
Starting fresh is the right call when a conversation has gone bad. But there’s a quieter problem that looks like the same thing and isn’t: a conversation that’s going fine but has simply run long, until Claude starts losing the early details. That’s next — and the fix there isn’t to throw the conversation out, but to tidy it up.