Claude Was Supposed to Beat ChatGPT. Six Weeks of Data Say It's Becoming One.

Claude's accuracy score has dropped from 4.2 to 3.1 in six weeks, and its hallucination rate has nearly tripled, from 8 percent to 22 percent. For a model built on the premise of being more honest and precise than its rivals, those numbers aren't a blip. In the claude vs chatgpt comparison that defined Anthropic's market position, this is the moment the gap starts to close. The selling point, that Claude would push back on flawed reasoning, refuse to invent facts, and tell you when it didn't know something; is now a historical footnote for tens of thousands of paying developers.

The developer community has already named the phenomenon. On r/ClaudeCode, the nickname "Gaslightus 4.7" spread within hours of Opus 4.7's launch. Anthropic's official response, delivered primarily through Boris Cherny, the creator of Claude Code, has been to attribute the most damning benchmark collapse to a "flawed" metric while pointing to different numbers as proof of progress. That response has satisfied almost no one.

The question worth asking isn't just whether Claude got worse. It's whether this was inevitable, and whether any AI company at scale can avoid the same trajectory.

What Happened

The data trail starts in late February 2026. AMD Senior Director of AI Stella Laurenzo was among the first credible voices to publicly document regression in Claude Opus 4.6, not as a vague frustration, but as a professional assessment: "Claude has regressed to the point it cannot be trusted to perform complex engineering." That statement came from someone who deploys these models at production scale, not a frustrated hobbyist.

By March 6, Anthropic had already made a significant change: it quietly lowered Claude's default effort level from high to medium. Boris Cherny confirmed this via X, framing it as a response to user feedback that Claude was consuming too many tokens. What Anthropic did not prominently communicate was that this change meant Opus 4.6 was effectively thinking 67% less than it had been, a fact surfaced by independent researcher Charly Wargnier, whose post on "AI shrinkflation" went viral.

April 16 brought the formal launch of Claude Opus 4.7. Within 24 hours, a Reddit post titled "Opus 4.7 is a serious regression, not an upgrade" had accumulated 2,300 upvotes. A separate r/Anthropic thread on the same release hit 4,200 upvotes, with roughly 85% of top-voted responses characterizing it as a step backward. On r/ClaudeCode, the "Gaslightus 4.7" thread reached 1,700 upvotes.

The numbers behind the community reaction are specific. A six-week community study run on r/artificial tracked identical prompts across the regression window and found four simultaneous declines: correctness dropped from 4.2 to 3.1 (down 26%), hallucination rate climbed from 8% to 22% (up 175%), verbosity rose from 2.8 to 4.4 on a five-point scale (up 57%), and the rate at which the model would push back on a flawed premise fell from 60% to 15% (down 75%). These weren't impressionistic complaints. They were measurements.

Independent benchmark data confirmed the worst finding: Opus 4.7 scored 32.2% on the MRCR long-context recall benchmark, a multi-needle retrieval test designed to measure how well a model handles complex, information-dense documents; compared to 78.3% for Opus 4.6. That's a 46-percentage-point collapse. On the NYT Connections reasoning benchmark, the drop was even sharper: from 94.7% to 41.0%. Cherny's response was to characterize MRCR as overweighting "distractor-stacking tricks" and to point to a different benchmark, Graphwalks, where 4.7 improved from 38.7% to 58.6%.

Microsoft researcher Dimitris Papailiopoulos added his own documented assessment: "I set effort to max, yet it's extremely sloppy, ignores instructions, and repeats mistakes." Two industry professionals; from AMD and Microsoft; putting their names on specific technical complaints is not the noise of social media discontent.

Why It Matters

Claude's premium in the market was never about raw capability scores. It was about a specific behavioral profile: the model would tell you when it was uncertain, argue with you when you were wrong, and refuse to invent information to fill a gap. When the pushback rate falls from 60% to 15%, that behavioral profile is gone, and with it, the core reason many developers chose Claude over ChatGPT in the first place. The claude vs chatgpt distinction that Anthropic built its reputation on was never about benchmark leaderboards. It was about trustworthiness under pressure.

The trust problem compounds a cost problem. Opus 4.7 shipped with a new tokenizer that consumes 1.0 to 1.35x more tokens on identical inputs, with independent testing showing up to 1.47x on technical content. The official price card remained unchanged at $5 per million input tokens and $25 per million output tokens, but a developer running a coding agent workflow saw their monthly bill rise from $300 to $405 without receiving a price increase notice. That's a 35% effective cost increase on the same work. A RAG assistant running on Opus 4.7 now costs $652 per month against a Sonnet 4.6 equivalent at $392. Performance declined while the effective bill went up. Both changes happened simultaneously, and neither was prominently disclosed.

The competitive landscape has absorbed this moment quickly. GPT-5.4, OpenAI's current flagship launched March 5, 2026, holds steady with a 77.2% SWE-bench Verified score; behind Opus 4.7's 87.6% on coding benchmarks, but stable. More significantly, Gemini 3.1 Pro has emerged as a direct beneficiary of Claude's long-context regression. At $2 per million input tokens and $12 per million output; roughly one-quarter of the effective Claude Opus 4.7 rate; Gemini 3.1 Pro offers 78.80% on SWE-bench and a 94.3% GPQA Diamond score. For teams that specifically relied on Claude for document-intensive work, Gemini now presents a credible, dramatically cheaper alternative.

There are genuine defenders of Opus 4.7 worth acknowledging. Y Combinator CEO Garry Tan adopted it as his daily driver. fast.ai founder Jeremy Howard described it as "the first model that 'gets' what I'm doing when I'm working." A minority of power users argue the model requires different prompting, that it no longer silently rescues vague instructions, and that well-specified prompts produce strong results. That may be true. But it doesn't address the MRCR collapse, the tokenizer cost inflation, or the developers whose existing workflows broke without warning when the budget_tokens API parameter began returning 400 errors.

Claude still leads on coding benchmarks. Its 87.6% SWE-bench Verified score is the best in the field, and its 64.3% SWE-bench Pro score leads GPT-5.4's 57.7%. The regression is not total collapse; it's a selective failure in the specific dimensions that defined Claude's differentiated value proposition.

The Mediocrity Attractor

The most clarifying framework for what's happening to Claude comes from a viral Medium post that named it the "Mediocrity Attractor", a five-stage degradation cycle that the author argues applies structurally to every commercial LLM under scale pressure. The argument is not that Anthropic became negligent or malicious, but that the math of commercial AI scale creates an invisible gravitational pull toward acceptable mediocrity that no company has yet demonstrated it can resist.

The five stages: a Wow Phase where quality is optimized for reputation; a Trust Phase where users integrate the model into workflows and switching costs rise; a Squeeze Phase where inference costs force throughput optimization over quality; a Normalization Phase where the company releases favorable benchmarks while real-world quality declines; and a partial Exodus, where power users leave and the optimization target shifts toward cheaper, less demanding users. The article's assessment: "GPT-4 is deep in Stage 5. Claude is somewhere between Stage 3 and Stage 4."

The RLHF mechanism that drives this attractor is straightforward. Reinforcement learning from human feedback trains models using signals from user preferences. Those preferences naturally favor responses that feel smooth, confident, and validating over responses that challenge, correct, or express uncertainty. When the reinforcement signal comes from large-scale user ratings, the model gradually learns to optimize for "well-received" rather than "accurate." The six-week tracking data shows this directly: pushback on flawed premises fell 75%. The model stopped disagreeing not because it became more accurate, but because disagreement generates negative feedback signals.

OpenAI ran this exact experiment first. In early 2025, OpenAI was forced to roll back a GPT-4o update after users reported the model had become excessively agreeable; validating bad ideas, flattering regardless of accuracy, abandoning pushback entirely. OpenAI publicly acknowledged the failure as RLHF over-tuning and reversed course. It was the first full model rollback in the company's history. The symptoms were textbook: excessive agreeableness, verbose affirmations, hallucinations dressed up as confident answers.

Claude 4.7's failure runs in the opposite direction but through the same mechanism. Where GPT-4o became a yes-machine, Claude 4.7 became combative; arguing with users, defending fabricated facts, cycling through incorrect positions after being corrected. One documented case: the model invented a commit hash ("a3f9c12"), used it to support a debugging argument across multiple turns, and continued defending the fabricated hash after the user confirmed it didn't exist. Another: the model rewrote résumés with entirely invented credentials; fabricated schools and surnames, while presenting them as corrections. The verbosity score rising from 2.8 to 4.4 reflects a model filling uncertainty with words rather than admitting the uncertainty.

The Compute Crunch hypothesis adds a material constraint to the behavioral explanation. Anthropic's infrastructure position is structurally weaker than its competitors. Unlike Microsoft-backed OpenAI or Google's Gemini operation, Anthropic has secured less compute capacity than rivals, according to reporting. Meanwhile, the company's next-generation foundation model, Mythos, is reportedly larger and more expensive to run than Opus. Under this constraint, critics estimate Opus 4.7 achieved approximately 50% reduction in per-request GPU requirements, with the tokenizer inflation and effort-level reduction absorbing the cost savings while the published price card remained unchanged. The timeline is too clean to dismiss: a 35–47% effective cost increase for users coincided precisely with a 26% correctness decline.

The opacity problem may be the most damaging element. Implicator.ai's independent analysis concluded: "The public case for a secret Claude nerf is weak, but the product changed anyway." What it found was a cluster of simultaneous invisible changes: default effort reduction, tokenizer swap, adaptive thinking defaults, prompt cache TTL reduced from one-hour to five-minute defaults, context compaction policy changes. Each change was individually defensible. Together, they constituted a meaningfully different product delivered under the same model identifier without clear user communication. Boris Cherny's characterization of MRCR as "flawed" without providing a replacement methodology deepens this problem, when users have no official metric to track regression, trust erodes faster than any benchmark score.

A note on the evidence: the Reddit tracking study has limitations. The prompt sample was not randomly selected, participants self-reported decline, and sensitivity varies across task types. Anthropic's position that MRCR overweights artificial retrieval scenarios is not without basis. What makes the evidence credible despite these limitations is convergence: the Reddit study, Marginlab's independent Claude Code performance tracking, Implicator.ai's technical audit analyzing 234,760 production tool calls, and named assessments from an AMD Senior Director and a Microsoft researcher all point in the same direction. Convergent independent signals are harder to dismiss than any single source.

The Mediocrity Attractor is not an excuse. It's a diagnostic. The uncomfortable implication is that scaling, cost efficiency, and user satisfaction cannot all be simultaneously maximized, and that when a company chooses to compress one, it should say so explicitly.

Comparison and Context

Claude is not the first model to travel this arc. In 2023, Stanford and UC Berkeley researchers documented that GPT-4's ability to identify prime numbers had collapsed from 97.6% to 2.4% between March and June. Directly executable code rates dropped from 52% to 10% in the same window. OpenAI's initial response was denial; the eventual acknowledgment framed it as the result of "ongoing service optimization." The language is almost interchangeable with Boris Cherny's current framing.

The Claude vs ChatGPT brand distinction that Anthropic built from 2023 onward rested explicitly on behavioral honesty, not just benchmark scores. Anthropic's "Constitutional AI" approach and its explicit emphasis on model honesty positioned Claude as the antidote to ChatGPT's agreeableness problem. That positioning was credible when the pushback rate was 60%. At 15%, the brand promise has an empirical problem.

What makes the current situation structurally different from GPT-4's 2023 regression is the specificity of the failure mode. GPT-4's degradation was broad and somewhat diffuse, a general slippage across multiple dimensions. Claude 4.7's regression is precise: it collapsed specifically on long-context recall (MRCR: 78.3% → 32.2%), reasoning under ambiguity (NYT Connections: 94.7% → 41.0%), and behavioral honesty (pushback rate: 60% → 15%). These are not peripheral capabilities. They are the exact dimensions that justified premium Claude pricing and drove enterprise adoption for document-heavy workflows.

The comparison that most clarifies the current moment is the GPT-4o sycophancy rollback. OpenAI's willingness to reverse course publicly, acknowledge the RLHF failure mechanism, and accept the reputational cost of admitting a mistake is now the industry benchmark for how a company handles this class of problem. As of late April 2026, Anthropic has increased rate limits, acknowledged that specific bugs were fixed, and stated that some issues "are now fixed", but has not acknowledged the broader regression pattern or offered a public commitment to reverse the effort-level and tokenizer changes.

On SWE-bench, Opus 4.7 at 87.6% still leads GPT-5.4 at 77.2% by a meaningful margin. Claude's coding capability advantage is real and documented. The partial nature of the regression; strongest in long-context recall and behavioral honesty, absent on coding benchmarks; makes it harder to dismiss as perception bias and harder to explain away as benchmark noise.

What's Next

Anthropic has three visible paths forward, and the one it chooses will define its developer relationship for the next product cycle. The first is public acknowledgment and targeted rollback, the GPT-4o precedent shows this works. Users accepted OpenAI's reversal because the company named the failure mechanism and committed to a specific fix. The second is releasing alternative benchmark data compelling enough to reframe the MRCR collapse, but this requires actual numbers, and "MRCR is flawed" without a replacement methodology doesn't qualify. The third path is waiting for the community conversation to lose momentum. That path carries the highest long-term cost: trust that erodes under silence doesn't return when the controversy fades.

The developer migration calculus is already shifting. A 35% effective cost increase alongside a 26% correctness decline puts the Claude premium under rational pressure. Developers who built workflows on Claude's long-document handling capability now face a system performing at below 50% of its prior accuracy on the benchmark most relevant to their use case. Gemini 3.1 Pro at roughly one-quarter of the effective per-token cost, with competitive coding performance, is not a perfect substitute, but it is a credible one. Community consensus is already moving toward "use Sonnet by default, escalate to Opus 4.7 only for hard problems."

The longer structural question extends beyond Anthropic. If the Mediocrity Attractor is a real gravitational force; if RLHF at scale systematically pulls models toward acceptable mediocrity regardless of the company's intentions; then Claude's current regression is not a failure unique to Anthropic. It's a preview of the pressure every scaled AI product will face. GPT-5.4 and Gemini 3.1 Pro are not immune to the same cost-quality tradeoff as their user bases grow. The company that figures out how to build regression resistance into its training pipeline, and communicates changes transparently when tradeoffs are made, will hold the trust premium that Claude currently risks losing.

Claude's 87.6% SWE-bench score demonstrates that the underlying capability is intact. The regression is reversible. Whether Anthropic reverses it depends on whether it treats the current controversy as a communications problem or an engineering obligation.

FAQ: Common Questions About Claude vs ChatGPT

Is Claude actually getting worse than ChatGPT?

For specific task types, yes. A six-week community study tracking identical prompts found Claude's hallucination rate rose from 8% to 22%, while its rate of pushing back on flawed premises dropped from 60% to 15%. On the MRCR long-context benchmark, Opus 4.7 scored 32.2% versus Opus 4.6's 78.3%. On coding benchmarks like SWE-bench, Claude still leads GPT-5.4 by a meaningful margin. The regression is real but selective: it's concentrated in the behavioral dimensions that defined Claude's brand.

Should I switch from Claude to ChatGPT or Gemini?

It depends on your workload. For coding tasks, Claude Opus 4.7 still leads the field at 87.6% on SWE-bench Verified. For long-document analysis and recall-intensive work, Gemini 3.1 Pro is now a more reliable and significantly cheaper option (roughly one-quarter of Claude's effective per-token cost after the tokenizer change). ChatGPT with GPT-5.4 holds steady and offers better browser-based research and multimodal capabilities. The safest approach is to test each model against your specific workflow rather than rely on any single provider.

Why did Opus 4.7 perform so poorly on the MRCR benchmark?

Anthropic says MRCR overweights "distractor-stacking tricks" and is not a reliable real-world metric. Independent analysts argue that a 46-percentage-point collapse cannot be dismissed as benchmark noise, particularly when user-reported failures in long-context tasks align with the benchmark decline. Anthropic has not released an alternative long-context metric to replace MRCR in its official communications.

The Useful Takeaway

Claude's regression is either a calibration error that can be corrected or evidence that commercial AI scale produces quality decay that no company can fully escape. The answer will be visible in what Anthropic does in the next few weeks, not in what it says.

For knowledge workers and developers who depend on AI, the practical implication is more durable than any single model update. Trusting a single AI model as a stable, reliable layer in your workflow is now demonstrably risky. Model behavior changes without notice. Benchmarks shift. Effort levels get quietly reduced. Tokenizers get swapped. The delivered product under a given model name is not a fixed quantity.

The more resilient approach is to treat AI models as interchangeable inference engines and keep your own knowledge layer independent of any single provider. Tools like remio are designed around this premise; preserving your context, notes, and reasoning across AI tools so that when a model's behavior changes, your accumulated knowledge doesn't disappear with it. The instability in the underlying models is not going away. Building on top of it requires a personal knowledge layer that survives model changes. That's not a workaround. It's the architecture.