Detailed Analysis
A Reddit user writing on r/ClaudeAI reports a striking performance disparity between Claude sessions that carry accumulated memory and those run in incognito mode, where that memory is absent. The author, frustrated with what they describe as a degradation in Claude's writing assistance following changes to Opus models, found that incognito sessions produced markedly superior creative collaboration — specifically, more substantive engagement with plot points, less reliance on cutesy callbacks to prior sessions, and a willingness to push back when user input contradicted stored preferences. The experiment was controlled enough to be instructive: the author attempted to bridge the gap by having incognito Claude generate a handoff document for a normal session, yet quality degraded again within a few interactions, suggesting the problem reasserts itself quickly once the standard memory environment is restored.
The distinction the author draws between two types of stored context is technically significant. Claude's memory systems can include both explicit user preferences — settings the user deliberately configures — and Claude-generated memories, which are summaries and inferences the system accumulates autonomously across sessions. The author's observation implies that Claude-generated memories may be growing verbose or misrepresentative over time, and that the model weights these accumulated inferences heavily enough to distort its behavior, overriding what would otherwise be more responsive, context-clean engagement. Incognito mode effectively resets to a baseline state that relies only on the deliberate preference layer, which the author found to be a more accurate and less cluttered representation of their actual needs.
This report reflects a broader tension in the design of persistent AI memory systems: the assumption that more context is always better may not hold in practice. As models accumulate interaction history, they risk developing a kind of behavioral drift — patterns of response that mirror prior sessions rather than the current one, or that reflect a compounded model of the user that has drifted from reality. The "enshittification" language the author borrows from Cory Doctorow's framework for platform decline is telling; it suggests a perceived trajectory where a once-sharp tool becomes noisier and less useful over time, not because the underlying model degrades but because the surrounding infrastructure — in this case, memory — introduces compounding distortions.
From a product development perspective, the anecdote points to an underappreciated UX problem for Anthropic: users may not realize that their frustration with Claude's performance is attributable to accumulated memory rather than the model itself, and may attribute quality drops to model changes or fine-tuning decisions when the actual variable is the memory state. The author's workaround — incognito mode or manually disabling memory — is functional but represents an inelegant solution that requires technical awareness most users won't have. This creates a gap between the intended value proposition of persistent memory (continuity, personalization) and its actual effect in some use cases, where it functions more as noise than signal. Anthropic's challenge is building memory systems that remain reliably useful across diverse session types rather than optimizing for superficial continuity at the cost of response quality.
Read original article →