The short version

Long sessions are not automatically better sessions. Claude must continue working with the conversation, instructions, files, and outputs that remain in context. Keep the material that changes the current decision and remove residue from completed work.

A four-part context practice

Keep

Retain the current objective, active constraints, critical evidence, and unresolved decisions. These are the materials Claude needs to reason about the work in front of it.

Compress

Replace completed discussion with a short durable summary. Record decisions, assumptions, and open questions without preserving every intermediate exchange.

Isolate

Move high-volume searches, logs, broad file inspection, or repetitive extraction into a separate working context. Return only the findings and evidence references needed by the main task.

Drop

Remove obsolete instructions, resolved exceptions, and finished-task detail. Starting a fresh session is often the cleanest choice when the objective changes.

Why the carrying cost matters

Irrelevant context can consume capacity and compete with current requirements. It can also make old assumptions feel more important than they are. The problem is not merely length; it is the ratio of decision-relevant material to accumulated clutter.

Example: recurring analysis

One permanent conversation for every monthly review appears convenient, but it mixes prior files, resolved issues, old exceptions, and current data. A better workflow begins each run with stable instructions, the current inputs, and a compact record of standing rules and unresolved items.

This preserves continuity of judgment without carrying continuity of debris.

Claude Code practices

  • Start a new session for a genuinely new task.
  • Compact when the same task continues but earlier detail no longer needs to remain verbatim.
  • Inspect startup context and remove instructions that are not broadly useful.
  • Point Claude to relevant files instead of forcing broad discovery when the scope is known.
  • Use separate workers for investigations that generate large temporary outputs.

A decision test

For every item in context, ask: would removing this material change the quality of the current decision? If not, summarize it, move it elsewhere, or remove it.

Try it

Choose a recurring workflow and list everything normally loaded into one long conversation. Classify each item as keep, compress, isolate, or drop. Then define the event that should trigger a clean session rather than another turn in the old one.