One Long Chat vs Five Short Ones
You have a thread that is ninety messages deep. It knows your project. It also still believes a decision you reversed on Tuesday, and it keeps quietly steering back to it.
The question is not whether long chats are good. It is when a thread stops helping and starts dragging — and what to do at that exact moment.
The one-sentence test
Try to state the current task in one sentence without scrolling up. If you cannot, the thread is over. Not because the model has run out of room, but because you have: you are no longer tracking what it is working on, which means you can no longer tell when it drifts.
This is a better signal than message count. Some threads are still sharp at two hundred messages because the task never changed. Others are already lost at fifteen.
When the long chat wins
**One artifact, edited repeatedly.** A document, a piece of code, a plan you are refining. Every earlier turn is context the model needs, and starting fresh means re-establishing it. Stay.
**Cumulative correction.** You have spent twenty messages teaching it what "too formal" means for you. That correction lives only in this thread. Throwing it away costs more than the drag.
When five short ones win
**The task changed.** You came in to fix a title and now you are writing a launch plan. Everything before the pivot is noise that the model still weighs — including the assumptions it formed from your first, narrower question.
**You reversed a decision.** This is the expensive one. A model does not "unlearn" the abandoned direction; it holds both and keeps offering compromises between them. If you changed your mind about something structural, the cheapest fix is a new chat that never heard the old plan.
**The answers got vaguer, not sharper.** Late in a long thread, replies often turn into summaries of the conversation instead of work on the task. That is the signal to cut.
The handoff that makes resetting cheap
Most people avoid new chats because re-explaining hurts. So do not re-explain — make the old thread do it:
Write a brief for a fresh chat that has none of this context. Ten lines maximum: the goal, the three decisions already made and why, what is explicitly out of scope, and the current state of the draft. No summary of our conversation — only what the next chat needs to act.
Paste that into the new thread and you keep the accumulated thinking without the accumulated wrong turns. It takes fifteen seconds and it is the entire trick.
The rule
Long thread while the task is the same and the corrections are compounding. Fresh thread the moment the goal moves or a decision flips. And never start over from nothing — always hand off with the brief.
Your chats are not a filing system, and the thread is not the work. If you are keeping a conversation alive because it feels wasteful to close it, that is the moment it started costing you.
Want the calm version of AI news like this, once a week? Subscribe to the Sharp AI Hub newsletter →