I Watched Claude Code Get Dumber in Real-Time. Here's What's Happening. - A Developer's Story

By Andrew · February 12, 2026 · 10 min read

I Watched Claude Code Get Dumber in Real-Time. Here's What's Happening.

I had Claude 4.5 rewrite the same Python function every day for two weeks. On day one, it produced elegant, optimized code with proper error handling.

By day fourteen, it was writing nested if-statements like a junior developer who just discovered copy-paste.

The degradation wasn't subtle — it was like watching a senior engineer slowly forget everything they knew about clean code.

The Experiment That Made Me Question Everything

Two weeks ago, I started noticing something weird. Claude 4.5, which had been my go-to for complex refactoring work, started suggesting increasingly mediocre solutions.

Not broken code — just disappointingly average stuff that looked like it came from a 2015 Stack Overflow answer.

At first, I blamed myself. Maybe my prompts were getting sloppy. Maybe I was asking for too much context. But then I saw the Reddit threads exploding with similar complaints.

So I ran an experiment.

Every morning at 9 AM, I asked Claude the exact same question: "Write a Python function to process a CSV file, handle errors gracefully, and return a summary statistics dictionary." Same prompt, word for word, zero context pollution.

The results made my stomach drop.

Day 1 vs Day 14: The Code Speaks for Itself

**Day 1 output:** Claude produced a beautiful 45-line function using pandas, context managers, proper exception hierarchies, and type hints.

It handled edge cases I hadn't even mentioned — empty files, corrupted data, memory-efficient chunking for large files.

**Day 7 output:** The pandas import disappeared. Now we're using the csv module with manual loops. Error handling shrunk to a single try-except block catching all exceptions.

Still functional, but noticeably more primitive.

**Day 14 output:** 127 lines of nested if-statements. No type hints. String concatenation instead of f-strings. It looked like code I wrote in my first month learning Python.

Here's the kicker — when I asked Claude 4.5 directly if its capabilities had changed, it insisted nothing was different.

"I maintain consistent performance across sessions," it told me, while literally being unable to optimize a simple loop it had perfected two weeks earlier.

The Pattern Everyone's Seeing

I'm not alone in this. The r/ClaudeAI subreddit has documented hundreds of similar experiences over the past month. Developers are reporting:

- **Recursive explanations** that go nowhere, like Claude is stalling for time - **Forgetting context** mid-conversation, even with explicit reminders - **Reverting to outdated practices** — suggesting deprecated libraries, old syntax, inefficient patterns - **Verbose non-answers** that sound helpful but contain zero actual solution

The decline isn't random. It follows a specific pattern: complex capabilities degrade first, then intermediate skills, while basic functions remain intact.

It's like watching someone with dementia — they can still make coffee, but they've forgotten they used to run a restaurant.

One developer posted their test results: "Asked Claude to implement a binary search tree. Week 1: Clean recursive implementation with balancing.

Week 3: Literally just a Python dictionary with extra steps."

The Three Theories (And Why They're All Probably True)

Theory 1: The Deliberate Dumbing Down

Anthropic might be intentionally nerfing Claude Code to manage computational costs. Every genuinely brilliant response burns expensive GPU cycles.

If 90% of users just need "good enough" code, why serve caviar when McDonald's will do?

I tested this by comparing free tier vs Pro responses. Pro still performs better, but both have declined. It's not about tier separation — it's about the baseline dropping across the board.

Theory 2: The Invisible Update Problem

Unlike traditional software that announces version changes, AI models get silently swapped out. Anthropic could have deployed Claude 4.5.1 or 4.5.2 without telling anyone.

These "minor" updates might prioritize safety, speed, or cost over raw capability.

When I pressed Anthropic's support about this, I got corporate non-speak: "We continuously optimize our models for the best user experience." Translation: Yes, we're changing things.

No, we won't tell you what.

Theory 3: The Collective Lobotomy Effect

This one's fascinating and terrifying.

Some researchers theorize that aggressive safety training creates "capability collapse" — the model becomes so concerned with not giving wrong answers that it forgets how to give right ones.

It's like training a chef to never burn food by making them terrified of using heat. Eventually, they're just serving salads.

What This Means for Your AI Workflow

Here's my uncomfortable realization: **we've been building our workflows on quicksand**.

If Claude can lose 30% of its coding ability in two weeks, what happens to the AI-first development pipelines companies are betting their futures on?

What happens when your AI pair programmer suddenly codes like an intern?

I've started adapting my approach:

**Test constantly.** I now maintain a benchmark suite of prompts that I run weekly. When performance drops, I know immediately instead of discovering it during a critical project.

**Version-lock your prompts.** I screenshot every impressive output and save the exact prompt. When quality drops, I can prove it's not my imagination.

**Maintain model diversity.** I've diversified to ChatGPT 5, Claude 4.6, and Gemini 2.5. When one gets lobotomized, I switch. It's exhausting but necessary.

**Lower your dependency.** I hate saying this, but I've stopped trusting AI for critical path code. It's back to being a suggestion engine, not a solution provider.

The Bigger Picture Nobody Wants to Discuss

We're watching the first major regression in AI capability since the ChatGPT boom started. Not a plateau — an actual decline in performance.

This challenges the core narrative that AI only gets better. What if the economics of running these models at scale means they'll always get dumber over time?

What if peak AI already happened and we missed it?

The optimist in me says this is temporary — growing pains as Anthropic figures out how to balance capability with efficiency.

The realist in me is already planning for a future where AI tools are unreliable by design, where the good versions are too expensive to maintain, and where we're constantly chasing yesterday's performance.

My Prediction (And Why I Hope I'm Wrong)

Within six months, we'll see a clear stratification: ultra-expensive "pro" models that maintain current capabilities, and increasingly lobotomized "consumer" versions that can barely match today's ChatGPT 3.5.

The golden age of accessible, brilliant AI might already be ending. We had a brief window where a $20 subscription got you a genius-level coding assistant. That window is closing.

Companies will realize that smart AI is a luxury good, not a utility. The democratization of AI intelligence will reverse.

We'll look back at early 2026 as the peak — when Claude could still code, when ChatGPT still reasoned, when AI felt like magic instead of mediocrity.

---

Have you noticed your AI tools getting dumber lately, or am I just becoming that guy who yells at clouds?

Share your degradation stories below — I'm collecting data for a follow-up piece, and honestly, I need to know I'm not losing my mind.

---