Detailed Analysis
A Reddit thread on r/ClaudeAI has surfaced a persistent complaint among power users of Claude Opus: the model's tendency to pad its responses with what one user calls "painfully AI-generated" filler language. Phrases like "Furthermore, delving deeper into the implementation reveals..." or "It is crucial to remember that a well-defined repository boundary is a testament to clean architecture" exemplify a stilted, over-formalized register that reads as distinctly non-human. The user notes this was especially pronounced in Opus 4.5, with only marginal improvement in the newer Opus 5 release, suggesting the issue is rooted deeply enough in the model's training or default behavior that version bumps alone haven't resolved it. The thread asks the community whether workarounds exist—custom agents, skills, system prompts, or third-party frameworks like "caveman" (a reference to tools designed to strip AI verbosity and force terser, more direct output).
This complaint reflects a broader tension in how large language models are trained and tuned. Models like Opus are typically optimized through RLHF (reinforcement learning from human feedback) processes that can inadvertently reward verbose, hedge-heavy, academic-sounding prose because such language often appears more "thorough" or "safe" to human raters during training, even when it adds no informational value. Over time, this creates a recognizable house style—sometimes derisively called "AI slop" or "GPT-ese"—characterized by throat-clearing transitions, unnecessary qualifiers, and a compulsion to state the obvious with faux-profundity. For developers and technical users who rely on Claude for code review, documentation, or rapid iteration, this verbosity isn't just an aesthetic annoyance; it slows down comprehension, buries actionable information, and undermines trust in the model's outputs, especially in agentic workflows where responses need to be parsed quickly or chained into further automated steps.
The mention of Opus 4.5 versus Opus 5 is notable because it implies Anthropic has been iterating on this specific behavior across model generations, even if imperfectly. This tracks with Anthropic's public positioning around "Claude's Constitution" and character training, where the company has explicitly stated goals around making Claude more direct, less sycophantic, and more genuinely useful rather than performatively verbose. The fact that users are still finding workarounds necessary—custom system prompts instructing the model to "cut the fluff," specialized skills, or external frameworks—suggests that default alignment tuning hasn't fully solved the problem at the product level, leaving the burden on end users to engineer around it.
This dynamic is emblematic of a wider trend in the AI industry: as models become more capable, the differentiator increasingly shifts from raw intelligence to communication style, tone calibration, and the ability to match register to context. Competitors face similar criticisms, and the "sounds like AI wrote it" tell has become a meme across writing, coding, and business communication. Anthropic's own marketing has emphasized Claude's supposed edge in natural, thoughtful communication, making community pushback like this thread particularly pointed—it's a signal that the gap between marketed personality and actual default behavior remains a live issue. Expect continued user-driven prompt engineering, third-party "de-AI-ify" tools, and pressure on Anthropic to bake terser, more human-sounding defaults directly into future Opus releases rather than requiring users to fight the model's instincts turn after turn.
Read original article →