Detailed Analysis
Users on Reddit's r/Anthropic community have begun flagging a recurring issue in which Claude appears to lose or "drop" earlier portions of a conversation within project chats, causing the model to misunderstand follow-up questions that depend on prior exchanges. The behavior manifests as earlier messages becoming inaccessible or functionally absent from Claude's active awareness, even within the same session. While the original poster frames it as potentially a bug, the phenomenon is documented across multiple platforms and Claude versions — including Claude 3.7 and Sonnet 4 — and stems from a combination of architectural constraints, compaction mechanics, and client-side resource failures rather than any single discrete defect.
The primary driver behind context loss is what researchers and practitioners have termed "context rot" — a degradation in model performance that accelerates as conversation length approaches the limits of the active context window. Claude's context window can reach up to 200,000 tokens in tools like Claude Code, but research by Du et al. (2025) confirms that performance begins deteriorating well before that ceiling, with measurable degradation emerging around 80% capacity. Crucially, the failure mode is tied to input length itself rather than to the model's ability to retrieve specific facts; even when relevant information is technically present in the window, the model's effective utilization of it declines. When sessions hit 100% capacity, context effectively crashes, producing the experience users describe — where Claude behaves as though earlier exchanges never occurred.
Compounding the architectural issue are client-side and tooling-specific failure modes. In Claude Desktop, responses can vanish mid-generation following inactivity periods or when processing large files, often the result of memory or CPU exhaustion and corrupted local cache data. Cursor users have reported mid-response "dropouts" that reset Claude to a state resembling a fresh session, sometimes correlated with network interruptions. Automatic compaction — a feature designed to summarize conversation history and free up token space — introduces its own risk through what has been described as "context pollution," wherein the compaction summary retains irrelevant details while discarding critical ones such as project decisions or earlier constraints established by the user. This creates a scenario where the model's apparent continuity is actually reconstructed from an incomplete or distorted summary of the original exchange.
Anthropic and the broader developer community have surfaced several mitigation strategies, though none fully resolve the underlying tension between context window limits and long-running conversations. Users are advised to monitor token usage via the `/context` command, selectively compact conversation history with `/compact` rather than relying on automatic triggers, and offload persistent project state to external files such as `CLAUDE.md` to reduce token pressure. Sub-agents can be deployed for token-intensive subtasks to preserve headroom in the primary session. These workarounds represent a form of manual context management that effectively asks users to compensate for architectural constraints through deliberate conversational hygiene — a non-trivial burden for casual users who expect chat continuity as a baseline feature.
The broader significance of this issue lies in what it reveals about the current state of long-context AI deployment. As users increasingly rely on Claude for extended, multi-turn projects rather than single-query tasks, the gap between the theoretical context window and the model's practical coherence over that window becomes a meaningful product liability. The Reddit thread reflects a growing segment of users encountering this gap not in controlled benchmarks but in everyday workflows, and their confusion — unsure whether the behavior is a bug, a known limitation, or user error — points to a communication and expectation-setting challenge that is as much about documentation and transparency as it is about engineering. Context reliability will likely become a key differentiator in enterprise AI adoption as these tools mature.
Read original article →