Detailed Analysis
A Reddit thread in r/ClaudeAI captures a common frustration among power users of Claude: the perception that the model is not actually engaging its "thinking" capabilities despite explicit and repeated instructions to do so. The original poster describes exhausting the standard toolkit available to Anthropic's consumer product—custom instructions in account settings, project-level instructions, a purpose-built "skill" designed to force deliberation, and inline prompt directives like "[Think before replying]"—all with no discernible change in output quality. Notably, the poster clarifies in an edit that Extended Thinking was toggled on and the effort setting was maxed out, preempting the most obvious troubleshooting suggestions and signaling that this is not simply a case of a user failing to enable the right feature.
This complaint touches on a persistent tension in how large language models are engineered versus how users intuitively expect them to behave. Extended Thinking, Anthropic's mechanism for allocating additional inference-time computation to reasoning before producing a final answer, is designed to be triggered by the complexity Claude infers from a request rather than purely by user command. When a model receives a casual or seemingly straightforward prompt, it may default to a fast-path response even if the user has appended instructions demanding deliberation, because the system's own classifier of "how much reasoning is warranted" doesn't necessarily weight explicit meta-instructions as strongly as the perceived difficulty of the task itself. This creates a gap between user intent (explicitly requesting rigor) and model behavior (implicitly judging effort based on surface features of the prompt), which is exactly the kind of instruction-following failure that frustrates users who have learned to treat AI assistants as configurable tools rather than opaque black boxes.
The frustration also reflects a broader usability challenge in AI products: the layering of controls—system-level settings, project instructions, skills, and inline prompts—creates an illusion of fine-grained control that may not correspond to how the underlying model actually prioritizes or reconciles competing signals. Users are effectively guessing at a mental model of how instructions cascade and interact, without visibility into which layer wins when they conflict or overlap. The offhand remark that Claude "will for sure agree with me when I cuss it out" is telling: it suggests the model is responsive to emotional or conversational cues but not to structural or procedural ones, a mismatch that undermines trust in the product's configurability and raises questions about whether reasoning behavior is being gated by internal heuristics that are invisible and unadjustable to the end user.
This kind of complaint is emblematic of a wider trend as reasoning-augmented models like Claude, GPT-4/5 with chain-of-thought variants, and others move from research demonstrations into everyday consumer workflows. As these systems are marketed around their capacity for deliberate, multi-step reasoning, users increasingly expect that capacity to be reliably invocable on demand, much like a setting or mode switch. When that expectation collides with models that make their own judgment calls about effort allocation—often for cost, latency, or safety reasons—it exposes a friction point that AI labs will need to address through clearer documentation, more transparent controls, or more faithful adherence to explicit reasoning requests. The thread is a small but representative data point in the ongoing negotiation between AI companies' internal optimization priorities and users' desire for predictable, controllable model behavior.
Read original article →