When to Compact?

Detailed Analysis

A Reddit thread in r/ClaudeAI captures a common point of confusion among Claude power users: when exactly should someone compact their conversation context, and why does the guidance seem so inconsistent? The original poster, a self-described non-coder who uses Claude Max (the $20/month tier) for document-heavy office work—reviewing large sets of files, spreadsheets, and scanned documents—describes running context windows up to 300-400k tokens before feeling compelled to compact or restart. Their core frustration is twofold: a lack of authoritative guidance on optimal compaction thresholds, and the meta-cost of interrupting productive work sessions to strategize with Claude itself about when and how to compact, effectively spending model time managing the model rather than doing the task at hand.

The confusion stems from real technical ambiguity. Claude's context window (200k tokens standard, with some tiers and API configurations supporting up to 1M) doesn't have a single "safe" threshold before performance degrades—degradation is gradual and task-dependent rather than a hard cliff. Anthropic and community power-users have observed that model quality can start to soften well before the hard context limit is reached, particularly on tasks requiring the model to synthesize or cross-reference information scattered across many turns—exactly the kind of workflow this poster describes (reading through full documentation sets, finding holes, producing consolidated output). This creates the "conflicting advice" the poster references: some users report no issues até 100k tokens, others say quality drops past 50k for reasoning-heavy tasks, and still others push past 400k for simpler retrieval-style work. The honest answer is that the right threshold is highly dependent on task type, document complexity, and how much the user needs precise recall of early-context details versus general thematic understanding.

This matters because it exposes a genuine gap in how AI coding/agent tools communicate their own limitations to non-technical users. The poster is not a developer; they're an office worker who has found Claude transformative for tasks like scanned-document review and spreadsheet analysis, but they're navigating context management without the mental models that engineers bring to similar problems (e.g., chunking, retrieval-augmented generation, or explicit state management). Anthropic's own documentation and the auto-compact feature are attempts to abstract this complexity away, but auto-compact triggers based on rough heuristics rather than task-aware judgment, which is part of why users still feel the need to manually intervene and second-guess the timing.

More broadly, this thread reflects a maturing pain point in long-context LLM usage: as context windows have ballooned from 4k-8k tokens a few years ago to hundreds of thousands or even a million tokens today, the bottleneck has shifted from "can the model hold enough information" to "does the model use that information reliably as volume grows." This is sometimes called the "lost in the middle" problem or context degradation, and it's an active area of research across the industry, not just for Anthropic. For power users doing sustained, high-stakes knowledge work—legal document review, financial analysis, large-scale editing—these questions about compaction timing are really proxies for a bigger unresolved question: how much can users trust a model's output fidelity as conversation length grows, and how transparent should vendors be about where that trust starts to erode. Until Anthropic or the community develops clearer, task-specific benchmarks for context reliability, threads like this will keep surfacing as users try to reverse-engineer best practices through trial, error, and shared anecdotes rather than firm documentation.