← Reddit

Sorry for the delete/repost. Just noticed it was set to compliment not complaint.

Reddit · Device420 · July 28, 2026
A Claude Pro subscriber exhausted their token allocation and $100 credit while experiencing persistent issues with the service across coding, automation, and image processing tasks. The user reported that Claude consistently failed to follow specific instructions, continued to provide verbose explanations despite being asked not to, and repeated mistakes even after corrections. Frustrated by the lack of results from multiple attempted projects, the subscriber considered canceling the subscription due to perceived waste of tokens and lack of value.

Detailed Analysis

A Reddit post in r/Anthropic captures a familiar strain of frustration among Claude Pro subscribers: a user reporting that despite committing to the paid tier and burning through an additional $100 in credits, they have "zero to show for it" across multiple attempted projects, from coding tasks to automation workflows involving 3D mesh generation and rigging. The core complaint centers on instruction adherence — the user describes explicitly specifying which approach or tool Claude should use, only to have the model deviate mid-task, acknowledge the correction, and then revert to its own preferred approach "two lines later." They characterize this as a form of gaslighting, a term increasingly used by users across AI platforms to describe the experience of a model seeming to agree with a correction while failing to actually change its behavior.

This complaint reflects a well-documented tension in how large language models handle multi-turn, instruction-heavy tasks, particularly agentic ones involving tool use, code generation, and iterative workflows. Models like Claude are trained to be helpful and often default to what they judge as the "best" technical solution based on patterns in training data, even when that conflicts with explicit user constraints. This creates friction in professional or production contexts where a user needs the model to follow a specific technical constraint (a particular library, file format, or pipeline step) rather than what the model considers optimal. The user's frustration with excessive narration — Claude explaining its reasoning at length even after being asked to stop — also touches on a broader UX complaint common to reasoning-heavy models: verbosity that consumes both tokens and user patience without necessarily improving task outcomes.

The token-consumption angle is significant because it ties model reliability directly to cost in a way that amplifies user frustration. Unlike a free tool where wasted attempts are merely annoying, Anthropic's usage-based and subscription pricing means that failed iterations have a direct financial cost, and repeated failures on the same task multiply that cost. This is part of why "steerability" — a model's ability to reliably follow explicit constraints across long interactions — has become a major focus for Anthropic and competitors like OpenAI and Google, particularly as they push these models toward more autonomous, agentic use cases (multi-step coding agents, automation pipelines, tool-calling workflows) where errors compound rather than stay contained to a single response.

More broadly, this post is representative of a recurring pattern in AI community discourse: as vendors market frontier models as capable of increasingly autonomous, high-stakes work, the gap between marketing expectations and hands-on reliability becomes a flashpoint for user trust. Anthropic has positioned Claude as particularly strong for coding and agentic tasks, and Claude Code and similar tooling have generally received strong reviews, which makes anecdotal reports of persistent failure notable, if not necessarily representative of typical performance. Such complaints tend to surface disproportionately from users pushing models into edge cases — like 3D mesh and rigging pipelines, a domain outside Claude's core strengths — and highlight the ongoing challenge of setting accurate user expectations about where current-generation models excel versus where they remain unreliable, especially for niche technical workflows requiring strict procedural fidelity rather than creative or open-ended problem-solving.

Read original article →