Opus 5 amnesia?

Detailed Analysis

A Reddit post in r/ClaudeAI titled "Opus 5 amnesia?" raises concerns about context retention in Anthropic's newest flagship model. The original poster describes Opus 5 as "extremely capable" but notably slower than its predecessor, with a recurring flaw: the model appears to lose track of decisions already made within a session. Specific examples cited include Opus 5 asking for approval on an action the user had already sanctioned, then re-explaining the rationale for that same action at length as though the conversation were starting fresh. In another instance, after an hour-long collaborative session moving a project from a sandbox environment to a live integration, the model asked whether the user was still working in sandbox mode—effectively erasing the progress of the entire session. When confronted about these lapses, the model reportedly backpedals and apologizes rather than demonstrating actual correction of its internal state.

This kind of complaint matters because context retention and state-tracking are foundational to how developers and power users evaluate coding and agentic AI assistants. Opus models are frequently used for extended, multi-step technical workflows—refactoring codebases, managing deployments, switching between environments—where the model's ability to remember prior decisions isn't a convenience but a functional requirement. If a model repeatedly "forgets" that a user has already approved a direction or confirms an environment state incorrectly, it introduces friction and risk: users must constantly re-verify what the model believes to be true, undermining the efficiency gains that agentic coding tools are supposed to provide. The gap between "great lengths of explanation" and actual retained state also suggests a mismatch between the model's verbal fluency and its grounding in the actual session history, a subtle but important distinction for users trying to trust the system's outputs during high-stakes operations like production deployments.

The tradeoff between capability and speed mentioned in the post is also notable. Larger, more capable models often carry higher latency, and if that added compute isn't translating into better memory or consistency within a session, users may reasonably question whether the increased capability is being allocated toward the right priorities. Context window management, summarization strategies, and how a model internally represents "what has already happened" in a long agentic session are areas where subtle regressions can appear even as benchmark performance on other tasks improves. This is a common pattern in frontier model releases: gains in reasoning or coding benchmarks don't always correlate with improvements in the more mundane, but practically critical, task of maintaining coherent state across a long interaction.

More broadly, this thread reflects a recurring theme in community discussion of frontier AI models—the gap between benchmark-driven capability claims and real-world, day-to-day reliability in agentic use cases. As AI assistants are increasingly deployed for complex, multi-turn technical work rather than single-shot question answering, issues like context amnesia become more visible and more costly. Community-sourced bug reports like this one serve as an informal but valuable signal to both Anthropic and prospective users about where a model's real-world performance may diverge from its marketed capabilities, and they often precede more formal acknowledgment or patches from the developer once patterns are corroborated across many users.