Detailed Analysis
A Reddit thread in the r/ClaudeAI community has surfaced growing user frustration with Claude Opus 5's verbosity, with one poster describing a pattern of "1,000 character minimum" replies laden with caveats, self-justification, and over-explanation for even routine tasks. The complaint centers not on the model's capability but on its communication style: users report a "stream of consciousness" quality to responses that forces them to wade through extended preambles and rationale before reaching the actual substance of what the model did. The original poster goes so far as to describe "a sense of dread" before opening task results, anticipating the effort required to extract actionable information from verbose output — a striking admission given that dread is typically associated with task difficulty, not with parsing a collaborator's explanations.
This complaint sits within a well-documented tension in large language model design between thoroughness and usability. As models become more capable of complex, multi-step reasoning and agentic task execution, they often generate more explanatory scaffolding — partly to justify decisions, partly to preempt follow-up questions, and partly as an artifact of training processes that reward detailed, cautious responses (including RLHF techniques that may inadvertently favor longer, hedge-heavy answers as "safer" or more helpful-seeming). For power users running Opus 5 in agentic workflows — the poster mentions a "Fable allowance," suggesting heavy, possibly paid or quota-based usage — this verbosity isn't just an aesthetic annoyance but a productivity tax, since each interaction requires cognitive overhead to separate signal from noise.
This concern matters because it touches on a core usability issue for developers and knowledge workers who rely on Claude for iterative technical work: code review, task execution, multi-turn agentic pipelines. In these contexts, response length and structure directly affect throughput. A model that reflexively explains "why grass is green" alongside completed work items forces users to either skim (risking missed caveats) or read fully (losing time), undermining the efficiency gains that motivated adoption of AI coding assistants in the first place. The fact that the complaint is framed as demotivating — reducing the poster's desire to use the tool on "anything" beyond primary projects — suggests verbosity fatigue can meaningfully suppress engagement, not merely annoy.
More broadly, this reflects an industry-wide struggle to calibrate model "personality" and output style as reasoning capabilities scale. Anthropic and competitors like OpenAI and Google have all faced similar community feedback cycles where flagship model upgrades introduce unwanted behavioral regressions — excessive hedging, sycophancy, or overexplanation — even as raw benchmark performance improves. Community threads like this one function as informal QA channels, often prompting subsequent system prompt adjustments, user-configurable verbosity settings, or fine-tuning updates. The fact that users are actively soliciting workarounds ("what are you guys doing to improve it?") signals both an expectation that Anthropic will eventually address the issue and a temporary reliance on prompt engineering — custom instructions demanding conciseness — as a stopgap, underscoring how much day-to-day usability still depends on user-side tuning rather than default model behavior.
Read original article →