AI Guides › Claude Mastery
The Honest Case For Starting Over Instead Of Fixing A Bad Thread
By Nigel Guy · 2 min read
There's a specific feeling of sunk cost that sets in four or five corrections into a conversation that's gone sideways — you've already put in the effort to steer it, so surely the next correction is the one that lands. Often it isn't. A thread that's drifted has usually drifted because something early on — a wrong assumption, an ambiguous first request, a misread piece of context — is still sitting underneath every message since, and each new correction is being built on top of it rather than replacing it.
The rule: if you've corrected the same misunderstanding twice and it's still recurring, the thread itself is the problem — starting fresh with what you now know is usually faster than a third correction.
The mechanism
- Count corrections on the same point, not corrections overall. One correction on one thing, then a different correction on a different thing, is just normal back-and-forth. Two corrections on the same underlying misunderstanding is the actual signal — it means the fix isn't sticking because something earlier in the thread keeps reasserting itself.
- Write down what you now know, before you abandon anything. The value of the bad thread isn't wasted — it's taught you exactly what needs to be stated clearly up front. Capture that in two or three sentences before you close the tab.
- Open a new conversation and lead with the corrected version. State the thing you had to explain twice as if it were the first sentence of the request, not an aside — "Assume X, not Y" stated up front, rather than buried as the fourth correction in a long thread.
- Don't paste the old thread in "for context." That's the single most common way people accidentally re-import the exact confusion they were trying to leave behind — the bad framing travels with the transcript unless you deliberately leave it out.
- Compare the result honestly. If the fresh thread, led with the corrected framing, gets there in one or two messages where the old one took six, that's the confirmation the restart was the right call, not just a feeling.
What to skip
Skip restarting after a single correction — that's just normal conversation, and treating every clarification as a reason to abandon ship is its own kind of overreaction. And skip restarting without capturing the lesson first; abandoning a confused thread without writing down what confused it means you're likely to recreate the same confusion in the new one, just with different wording.
Guardrails
- This is a judgement call based on a pattern, not an exact threshold — "twice" is a useful rule of thumb, not a rigid rule that applies identically to every kind of task.
- Starting over costs you the parts of the old thread that genuinely were working, not just the parts that were confused. Weigh that against the cost of continuing to patch, rather than treating a restart as free.
- None of this fixes a request that was genuinely under-specified from the start — see "Vague Requests, Vague Answers." A clearer restart still needs to actually be clear; simply being a fresh thread isn't what fixes it.
All 751 AI guides · JulieMango plans from £17/mo