AI Guides › Claude Mastery
When To Start A New Conversation (And Why More People Should)
By Nigel Guy · 2 min read
People treat a single chat like a physical notebook — you keep writing in the one you've already got open, because starting a new one feels like losing your place. So one thread ends up covering a first draft, then a completely different follow-up question, then an unrelated task from three days later, all stacked on top of each other. It doesn't feel like a problem in the moment. It shows up later, as answers that quietly drift or contradict something from twelve topics ago in the same thread.
The rule: a conversation should track one piece of work, not one calendar week — when the topic changes, the conversation should change with it.
The mechanism: the topic-boundary test
Ask this before your next message in an existing thread, not after:
- Is this the same task as when the conversation started? Same document, same decision, same piece of code — continue. A different one — new conversation.
- Would I need to explain this to a colleague as "a new thing," or as "more on what we were doing"? If it needs its own sentence to introduce, it's a new conversation.
- Has enough unrelated material piled up that finding the relevant bit means scrolling? If you're already hunting for the right message, the thread has stopped being useful as a record.
- Am I keeping this thread open mainly because I don't want to lose the context, not because the topic continues? That's the tell that you actually want a Project or a saved reference document — see "Turning A Conversation Into Something You Can Reuse" — not a longer single chat.
If two or more of these say "new," start a new conversation. Don't wait for a natural stopping point that may not arrive.
What to skip
Don't start a new conversation purely to "clean up" — hopping to a fresh thread every few messages just to keep things tidy loses genuinely useful continuity for no benefit, and re-explaining context you'd already established is its own cost. And don't confuse a long conversation with a bad one — depth on one real task, even across many messages, is exactly what a single thread is for. Length isn't the problem; unrelated content stacked inside one thread is.
Guardrails
- Whether a given surface keeps a record of old conversations, for how long, and whether they're searchable, is a product detail worth checking directly rather than assuming — this affects how comfortable you should be closing a thread versus keeping it open as a reference.
- Starting fresh doesn't erase what you've already learned about the problem — that lives in your own notes, in a Project's knowledge if you've set one up, or in memory if it picked up the relevant preference. A new conversation is a reset of clutter, not a reset of everything useful.
- This is a judgement call, not a rule with a hard threshold. Use the test above as a prompt to actually decide, not as a formula that removes the decision.
All 751 AI guides · JulieMango plans from £17/mo