Detailed Analysis
A Reddit user posting to r/Anthropic has articulated a sentiment that has grown into a recognizable thread of community feedback since Claude Opus 4.7's April 16, 2026 launch: that the newer model, despite superior benchmark scores, underperforms its predecessor in practical coding workflows. The poster reports that using identical CLAUDE.md configuration files and constraints, Claude Opus 4.6 continues to produce lean, usable code output, while 4.7 generates what they describe as "reams of dense verbosity" with little actionable result. Critically, the user draws a distinction between 4.7's coding performance — which they find disappointing — and its behavior in other domains, where they acknowledge it has shown genuine improvement. Their closing warning to Anthropic is pointed: do not deprecate 4.6 until a model is available that meaningfully surpasses it across the board, or risk driving users back to competing tools like OpenAI's Codex.
The user's frustration maps onto a documented and technically grounded tension in the 4.7 release. While Anthropic's own benchmarks show Claude Opus 4.7 scoring 87.6% on SWE-bench Verified versus 80.8% for 4.6, and resolving three times more production-grade tasks without intervention in Rakuten's testing, those gains come with significant real-world complications. Chief among them is a stricter instruction-following architecture: 4.7 treats bullet-pointed instructions as hard requirements rather than soft guidelines, which means prompts and configuration files carefully tuned for 4.6's looser interpretation can break or produce unexpected verbosity when carried over unchanged. The poster's experience of 4.7 generating voluminous but unusable output is consistent with this dynamic — a well-optimized 4.6 setup is not automatically a well-optimized 4.7 setup, and the migration cost is non-trivial. Anthropic has not made this compatibility gap prominently visible in its documentation, which the user explicitly flags as a product communication failure.
The cost dimension compounds the friction. Claude Opus 4.7 uses up to 35% more tokens per request due to tokenizer changes, and its default "xhigh" effort level in Claude Code — designed to enable deeper reasoning for agentic tasks — can increase real-world costs by 10 to 40% on complex workflows. For users who are not running vision-heavy tasks or long autonomous multi-step agents — the use cases where 4.7's improvements are most pronounced — these cost increases arrive without commensurate benefit. The model's architectural gains in areas like 3x resolution image handling, improved deductive logic in looping workflows, and pixel-accurate diagram generation are genuinely impressive, but they are irrelevant to a developer primarily doing iterative code generation in a familiar, well-tuned environment. Anthropic's own guidance implicitly acknowledges this: it recommends staying on 4.6 for short, conversational, or single-turn tasks.
Broader context positions this user complaint within a recurring pattern in large language model releases, where benchmark performance and user-perceived performance diverge due to qualitative factors that standardized tests do not capture — tone, verbosity calibration, prompt sensitivity, and workflow integration. Anthropic faces a specific version of this challenge because Claude Code has become a serious productivity tool for a segment of developers who have invested significant effort in configuration and prompt engineering. For that cohort, a model transition is not merely a technical upgrade but a workflow disruption, and the value proposition must be demonstrated concretely, not assumed from benchmark tables. The poster's implicit request — that Anthropic surface "secret sauce" configuration changes prominently, or bake them into defaults — reflects a reasonable expectation that the company should smooth the migration path rather than place the full burden of re-optimization on users.
The episode underscores a strategic tension Anthropic will continue to navigate as its model cadence accelerates: how to serve two distinct user populations simultaneously — early adopters and power users seeking frontier capability, and practitioners who have optimized deeply around existing behavior. Deprecating 4.6 prematurely, as the poster warns against, would risk alienating a segment of Claude Code's most engaged users at precisely the moment when competition from alternatives like Codex and other agentic coding tools is intensifying. Maintaining dual model availability is the more cautious path, but it carries its own costs in infrastructure and support complexity. How Anthropic balances these pressures in the months following 4.7's launch will be a meaningful signal about the company's priorities as it moves from AI research organization to AI product company.
Read original article →