Why Do AI Coding Assistants Get Worse Over Time? The Model Degradation Problem Explained

May 29, 2026

Problem

I’ve been using Claude Opus 4.6 since February 2026 for my daily coding work. It was great at first — multi-step refactoring, debugging tricky race conditions, writing integration tests. Then, around mid-March, I started noticing something off.

The model seemed… lazier. It gave shorter answers. It skipped steps. It said “I’ll leave that as an exercise for you” more often. I thought maybe I was imagining it, or my prompts had gotten worse.

But I wasn’t alone. A Reddit thread on r/codex with 220 upvotes captured the exact same frustration:

“I notice declines in both OpenAi and Anthropic models, usage limits are getting worse regardless of what I pay. I’ve tried switching between GPT and Claude and back again, but both seem to have gone down in quality.”

The thread title says it all: “Why does it feel like things are getting worse?”

The Quantified Evidence

The suspicion that models degrade after release is no longer just a feeling. In April 2026, AMD director Stella Laurenzo published an analysis of 6,852 Claude Opus session logs. The numbers were startling:

Metric	February 2026	April 2026	Change
Reasoning depth (average steps)	100% (baseline)	33%	-67%
BridgeBench accuracy	83.3%	68.3%	-15 points
BridgeBench global rank	#2	#10	-8 positions
Error hallucination rate	Baseline	+98%	~2x increase

This wasn’t user paranoia. The model I was using had measurably gotten worse — and the version number hadn’t changed.

Bar chart comparing Claude Opus 4.6 performance metrics between February 2026 and April 2026, showing reasoning depth dropping 67%, BridgeBench accuracy falling from 83.3% to 68.3%, and error hallucination rate increasing 98%.

The Three Root Causes

1. Inference Cost Optimization

AI providers serve models from a pool of compute nodes. To reduce serving costs, they can silently deploy lower-precision quantized variants or reduce the “thinking budget” per request.

Anthropic later admitted they lowered the default reasoning effort from High to Medium on March 4, 2026. This change saved roughly 40% per-request compute. But it also made the model stop doing multi-step reasoning. Users noticed immediately — shorter answers, surface-level explanations, less thorough code reviews.

Feb 20: Release - High reasoning, accurate
Mar  4: Reasoning effort lowered High → Medium
Mar 26: Cache bug introduced (memory loss)
Apr 16: Reply length cap imposed
Apr 24: Anthropic admits bugs, starts fixing

2. Engineering Regressions

Changes to the system prompt, safety classifiers, or prompt pipeline can silently degrade quality. In Claude’s case, three bugs stacked:

Reasoning effort reduction (March 4) — made the model lazier
Cache corruption (March 26) — caused the model to lose conversation context mid-session
Reply length cap (April 16) — a 25-word reply cap between tool calls reduced code quality by ~3%

These regressions didn’t just add up — they compounded. Users reported a “cumulative degradation” where each week felt worse than the last.

Timeline diagram showing three compounding regressions from March to April 2026: reasoning effort reduction, cache corruption bug, and reply length cap imposition, with annotation that each bug worsened the cumulative effect.

3. Resource Reallocation

When a company releases a new model, compute resources shift toward it. Older models run on fewer, lower-priority nodes — increasing latency and reducing reliability.

This is invisible to users. You see the same model name in your chat interface, but the backend serving it might be a smaller, slower, more congested cluster. The Reddit user who said “certain times of the day” the model works better was likely observing compute contention patterns — when US business hours hit, the older model gets squeezed.

The “AI Shrinkflation” Cycle

One Reddit comment summarized the pattern perfectly:

“It’s the circle of LLM — Shittify the current Model -> Release new model -> ‘OH WOW IT’S SO AMAZING’”

This became known as “AI Shrinkflation” — paying the same subscription price for silently reduced intelligence. The pattern repeats:

Circular diagram illustrating the AI Shrinkflation cycle: new model launches with impressive benchmarks, cost optimization and regressions degrade quality over months, users notice and complain, company releases a new model version, users celebrate the improvement, and the cycle repeats.

New model launches with impressive benchmarks
Over months, cost optimization and regressions degrade quality
Users notice and complain
Company releases a “new” model version
Users celebrate the improvement
Cycle repeats

Why This Matters for Developers

Lost productivity. You design prompts and workflows around a model’s capability. When it degrades, you need to constantly adapt — longer prompts, more manual review, more iterations.

Trust erosion. The biggest damage isn’t the temporary quality drop. It’s knowing that the tool you rely on might silently change without warning or recourse.

Billing asymmetry. Degraded models consume the same (or more) tokens. With Claude Opus, users reported burning through their entire monthly limit in under an hour on some degraded sessions.

No recourse. You cannot pin model versions. You cannot audit backend changes. There’s no contractual guarantee that “Claude Opus 4.6” today performs like it did at launch.

What You Can Do

There are practical steps to reduce your exposure:

# Track model behavior over time to detect regressions
import json
import datetime

def benchmark_model(client, test_prompts, model_id):
    """Simple regression detection for your own usage."""
    results = []
    for prompt in test_prompts:
        start = datetime.datetime.now()
        response = client.messages.create(
            model=model_id,
            max_tokens=1000,
            messages=[{"role": "user", "content": prompt}]
        )
        elapsed = (datetime.datetime.now() - start).total_seconds()
        results.append({
            "prompt": prompt[:50],
            "response_length": len(response.content[0].text),
            "latency": elapsed,
            "date": datetime.date.today().isoformat()
        })
    return results

# Run weekly and check for regressions
# Score below baseline? Investigate whether model quality has changed

Other things to consider:

Maintain a baseline. Save your model’s output on a standard test set when you first start using it. Compare monthly.
Don’t churn blindly. Jumping between providers doesn’t solve the systemic problem — they all do this.
Consider open-source alternatives. Self-hosted models (like Llama or DeepSeek) give you version control. You decide when to upgrade.
Voice your concerns. Public pressure works — the Claude Opus fix was only released after the data went viral.

Summary

In this post, I explained why AI coding assistants silently degrade after release. The 2026 Claude Opus scandal provided the first quantified evidence: reasoning depth dropped 67%, BridgeBench accuracy fell from 83.3% to 68.3%, and error hallucinations increased 98%. Three systemic causes drive this — cost optimization (reduced reasoning effort), engineering regressions (cache bugs, prompt limits), and resource reallocation (newer models get priority compute). Track your own session metrics, avoid over-reliance on any single provider’s “same version” guarantee, and consider open-source alternatives for critical workflows.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

👨‍💻 Reddit Discussion: Why does it feel like things are getting worse?
👨‍💻 Stella Laurenzo - 6,852 Session Logs Analysis
👨‍💻 Anthropic Claude Opus Degradation Statement (April 24, 2026)
👨‍💻 BridgeBench Leaderboard

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!