Context Optimisation: Managing Long Conversations

Series: Claude Learning Journey · Advanced Usage

Every message in a Claude session consumes context. The conversation history, the files you share, the system instructions — all of it lives in the context window. As sessions grow, context density changes. Useful context gets buried. Irrelevant context accumulates. The result is degraded performance and higher costs.

Long conversations need active management. This is not a passive process — you need to think about what is in context, what should be removed, and what should be added. Done well, a long session stays as useful as a fresh one.

The Context Budget Mentality

Think of your context window as a budget. Every token you spend on context is a token that is not available for new work. The goal is to spend that budget on high-signal, high-relevance content.

When you paste a 2,000-token file into a session to make a 50-token change, you are spending 2,000 tokens of budget on context that will matter for approximately one message. That is wasteful. The alternative: share the specific function, not the file. Share the error message, not the entire stack trace.

Pruning the Conversation

Claude sessions accumulate dead weight. Old context that was relevant at the start of a session becomes irrelevant by the end. Claude cannot automatically prune — you have to do it.

The pruning patterns that work:

Explicit summarisation: “We have covered a lot in this session. Summarise what we decided and what we are working on in two sentences. Start the summary from this point.”

Selective restarts: if a session has drifted far from its original topic, a new session with a fresh context window and a summary of the previous session is often better than continuing.

Archive and move on: when a task is complete, move to a new session rather than continuing to add context.

Knowing When to Restart

Every conversation has a natural lifespan. Claude sessions are not indefinite — at some point the accumulated context becomes noise rather than signal. The practical test: if Claude’s recent responses are lower quality than its earlier responses in the same session, the context has likely degraded.

When to restart:

• When you have completed the original task and moved on to something different
• When Claude starts giving generic responses rather than specific ones
• When the conversation is longer than 50-100 turns
• When you notice yourself re-explaining context that should already be established

What You’ll Learn

• The context budget mentality
• How to prune conversation history without losing important decisions
• When to start a new session versus continuing
• The signals that indicate context degradation

Try It Yourself

Take a long-running Claude session and evaluate it by the context budget test. How many of the tokens in context are actively useful for the current task? If less than half, the session is bloated. Write a summary, start a new session, and see whether Claude is more useful with fresh context and the summary.

What’s Next

Context management becomes more important as you spend more on each query. The next post is about the cost dimension — how to think about what Claude costs and how to reduce that cost without sacrificing quality.

---

Part of the Claude Learning Journey series · Next: Cost Optimisation: Getting the Most Value from Claude