Managing context in a long Claude conversation

Why a long conversation doesn't just keep getting smarter

It's tempting to assume more conversation history is unambiguously good — more context should mean better-informed responses. In practice, a conversation that's run a long time accumulates content that's no longer relevant alongside content that still is, and past a point, relevant information has to compete for attention against everything else that's built up, which can make responses feel less sharp on a task that hasn't actually gotten harder — only the conversation carrying it has gotten longer and noisier.

The signs a conversation has outgrown itself

A few patterns reliably indicate a conversation has accumulated more than it should be carrying: responses that seem to have forgotten something stated clearly earlier, answers that feel generic relative to how specific the conversation used to get, or a general sense that recent turns aren't building coherently on what came before. None of these individually proves the conversation has a context problem, but together, especially if they're new in an otherwise-long conversation, they're worth treating as a signal rather than pushing through with more of the same approach.

Summarising rather than just accumulating

Periodically consolidating what's actually still relevant — the decisions reached, the constraints established, the current state of the task — into a compact summary, and treating that summary as the effective starting point going forward, keeps a long-running task coherent without carrying every intermediate step that led there. This is a deliberate habit worth building for any task you expect to run long, not just a recovery step for a conversation that's already gotten unwieldy.

Starting fresh is sometimes genuinely better than continuing

Not every long conversation is worth rescuing with a summary — if a conversation has drifted far enough, or accumulated enough dead ends and abandoned approaches, starting a new conversation with a clean, deliberately curated context can be faster and more reliable than trying to reconstruct coherence inside the existing one. There's no cost to abandoning a conversation's history if a fresh start with the essential context restated gets you to a better result faster.

Building this into how you work on anything long-running

Treat context management as an active, ongoing part of any task that's going to span many turns, not a problem you only address once something's already gone wrong. A habit of periodically checking "does this conversation still have a clear, coherent picture of the goal" catches drift early, while a light summary fixes it — far cheaper than discovering the drift only once responses have already gotten noticeably worse.

Splitting a task by concern, not just by length

A conversation that's grown unwieldy isn't always best fixed by simply summarising and continuing — sometimes the actual problem is that it's carrying more than one genuinely separate concern at once, and splitting it into separate, focused conversations by concern produces better results than continuing to manage the length of a single conversation that was never really one task to begin with. If a long conversation feels like it's juggling several unrelated threads, consider whether it should have been several conversations from the start rather than treating the length itself as the only problem to solve.

Recognising the pattern before it costs you real work

The cost of unmanaged context growth compounds the longer it goes unaddressed — a conversation that's mildly diluted is a minor inconvenience, while one that's badly diluted can produce a result confidently wrong enough that you don't catch the error until real work has already been built on top of it. Catching the pattern early, before it reaches that point, is considerably cheaper than discovering it retroactively once a flawed result has already propagated into something else.

See debugging a stuck Claude Code session for the same underlying problem in a development-specific context, where the same context-management discipline applies.