Context & Reasoning/Context Engineering
Intermediate7 min

Conversation Hygiene for Long Sessions

Long sessions degrade. The file path assumptions get fuzzy, earlier instructions fade, and Claude starts contradicting decisions it made an hour ago. These practices prevent that — or help you recover when it happens anyway.

Quick Reference

  • →Name sessions at start: claude -n 'auth-migration' — easier to /resume and organize
  • →One task per session — context from earlier tasks pollutes later ones
  • →Check /context proactively at 50–60% capacity, not reactively at 90%
  • →'New task:' prefix when switching — resets Claude's mental model without /clear
  • →Write a handoff doc before ending a productive long session
  • →Put 'Compact Instructions' in CLAUDE.md to control what compaction preserves
  • →Context drift: Claude silently stops honoring earlier decisions as they age in context
  • →The auto memory system bridges sessions — use it for cross-session preferences and feedback

Why Long Sessions Degrade

A fresh session is Claude at its best. A 3-hour session with 15 file reads, two compaction cycles, and a dozen task switches is Claude at its most unreliable. The degradation is gradual, invisible, and by the time it is obvious it has already cost you.

  • ▸Context fills with irrelevant tool outputs from earlier tasks — Claude reasons over everything, not just what matters now
  • ▸Earlier decisions get compressed into summaries that lose nuance — 'we decided to use DynamoDB for sessions' becomes a vague note rather than a reasoned decision
  • ▸Corrections from turn 5 are not in the active context by turn 60 — Claude reverts to its original approach
  • ▸File content assumptions from a read 50 turns ago may differ from current file state
  • ▸Slower responses — larger context means more tokens to process per turn
Context Drift Is Silent

Claude does not say 'I have forgotten your earlier instruction.' It simply starts behaving as if the instruction never existed. Context drift — Claude silently reverting to older behavior — is often mistaken for a bug or misunderstanding when it is actually just a session that has outlived its effective lifespan.