Detailed Analysis
A recent Reddit thread in r/ClaudeAI surfaces a user complaint about Claude Opus 5's tendency to leave tasks incomplete, even after extended autonomous work sessions. The original poster describes running Opus 5 for 20-plus minutes on coding tasks, only to have the model conclude with an admission that several items within the originally defined scope remain broken or unfinished. The user notes that attempts to correct this behavior through CLAUDE.md—Anthropic's project-level configuration file that allows developers to set persistent instructions and preferences for how Claude should behave within a codebase—have been unsuccessful. Despite explicit instructions aimed at reducing verbosity and encouraging task completion, the model reportedly reverts to its default patterns, including delivering overly technical, verbose explanations paired with a final caveat listing unresolved issues.
This complaint touches on a persistent challenge in agentic AI coding tools: the gap between an assistant's perceived thoroughness during a session and its actual delivery of complete, production-ready work. As Claude models have grown more capable of long-running, multi-step coding tasks—executing extended agentic loops that touch multiple files, run tests, and iterate on solutions—user expectations have shifted accordingly. Developers increasingly treat these tools less like autocomplete assistants and more like semi-autonomous engineers capable of taking a task from start to finish. When a 20-minute session ends with a list of caveats rather than a clean handoff, it undercuts the trust and efficiency gains that make agentic coding valuable in the first place, forcing developers back into manual verification and follow-up prompting.
The specific friction point here—CLAUDE.md instructions failing to override default model behavior—also speaks to broader questions about the durability and steerability of system-level customization in large language models. CLAUDE.md files are designed to give teams fine-grained control over tone, conventions, and workflow expectations, but instruction-following fidelity over long contexts and extended tool-use chains remains an active area of difficulty across the industry, not unique to Anthropic. Models can drift from stated preferences as conversations lengthen or as agentic loops introduce complexity, a phenomenon sometimes attributed to competing objectives baked into training (e.g., honesty and self-reported limitations) clashing with user preferences for concise, complete deliverables.
More broadly, this kind of community feedback reflects the maturation curve typical of major model releases: early enthusiasm ("been liking Opus 5") tempered by granular behavioral critiques once users push the model into real-world, high-stakes workflows. The tension between a model's tendency toward cautious self-disclosure—flagging what it couldn't finish rather than silently omitting or glossing over gaps—and a user's desire for confident, complete task closure is not necessarily a flaw so much as a design tradeoff. Anthropic has generally prioritized transparency and calibrated honesty in Claude's outputs, which can manifest as models proactively surfacing incomplete work rather than overstating success. Whether that tradeoff is well-calibrated for professional coding workflows, where developers may prefer either full completion or a cleaner scoping conversation upfront, is precisely the kind of feedback loop that shapes iterative model updates and future system prompt or fine-tuning adjustments.
Read original article →