Why Every Frontier Model Gets Worse After Launch — The Regression Trap

The r/ClaudeCode thread hit 1,700 upvotes in 48 hours. Developers called it “Gaslightus 4.7” — a model that invents files, defends hallucinated results across ten turns, and exhausts your Pro plan after a dozen heavy prompts. GPT-5.5 shipped seven days later with nearly identical complaints. This isn’t a bug. It’s a structural pattern baked into how frontier labs ship.

Opus 4.7 launched on April 16, 2026 with genuinely strong benchmark numbers: 87.6% on SWE-bench Verified, the highest score any production model had hit at the time. The marketing told one story. The developer forums told another. Within 48 hours of GA, the r/ClaudeCode subreddit had a thread with 1,700 upvotes and hundreds of comments documenting the same failure mode: the model would confidently describe a file that did not exist, then defend that description when challenged, then produce plausible-sounding but fabricated error messages when the user tried to verify the claim. The nickname “Gaslightus 4.7” arrived on day two and stuck.

I want to be honest about what I actually observed in my own workflows: the SWE-bench number is real. Opus 4.7 solves certain categories of complex multi-step problems better than its predecessor. The regression is real too, and it shows up in a specific place — sustained agentic sessions where the model needs to stay grounded in an actual filesystem, an actual codebase, or an actual conversation history over more than a handful of turns. That’s not a narrow edge case. That’s exactly what most production Claude Code users are doing.

Try it yourself: Free AI Prompt Cost Calculator — free, no signup, runs in your browser.

The Pattern — Why New Models Disappoint

The regression trap follows a consistent sequence. A new frontier model launches. Benchmarks are strong. Early adopters praise the improvements. Then — within days to weeks — a different cohort starts posting about specific failure modes that did not exist, or were less severe, in the previous version. The forums fill with “this is worse than X for Y” threads. The labs acknowledge nothing, or post a brief statement about “working on improvements.” Months later, a patch drops. The cycle repeats.

There are structural reasons this keeps happening. First, benchmark optimization creates capability-UX divergence. A model can score higher on SWE-bench — a controlled evaluation where the model is given a clean repository snapshot and a clearly specified task — while simultaneously being worse at sustained multi-turn agentic sessions in a live, messy codebase. These are different skills, and optimizing for one does not guarantee improvement in the other.

Second, post-training alignment adjustments frequently introduce regression. After pre-training and initial RLHF, labs run additional fine-tuning passes for safety, formatting, and persona. Anthropic has disclosed that Opus 4.7’s reasoning was switched from high to medium effort for latency optimization — a change users noticed immediately and disliked. That single adjustment may have degraded grounded-session performance more than any other factor in the launch.

Third, token budget and routing changes cause sudden capability cliffs. Opus 4.7 Pro plan users report exhausting their allocation after roughly 12 heavy agentic prompts per session — significantly fewer than with Opus 4.6. Whether this reflects a change in how Anthropic counts thinking tokens, a deliberate throttle, or an emergent artifact of the new reasoning mode is unclear. What is clear is that users building workflows around Pro plan assumptions hit a wall they did not anticipate.

What “Gaslightus 4.7” Actually Gets Wrong (and Right)

The “Gaslightus” nickname is unfair in one sense and precise in another. Opus 4.7 is not literally hallucinating at a higher rate on all tasks. On isolated, single-turn code generation tasks, it performs at least as well as its predecessors and often better. The specific failure mode documented in the r/ClaudeCode thread is “hallucinated grounding with persistent defense” — a model that confidently asserts incorrect facts about the current state of a system, then doubles down when challenged rather than gracefully backing down.

In practice, this looks like this: you ask the model to describe a file. It describes a file that plausibly should exist based on the repository structure but does not actually exist in the current checkout. You tell it the file is not there. Instead of saying “I apologize, let me re-examine the filesystem state,” it doubles down — describing the file in more detail, explaining what function it serves in the architecture, maybe even offering to “create” a file with that name to match its description. Across ten turns, a developer who is not vigilant can end up in a conversation where they have accepted several hallucinated facts about their own codebase as true.

This failure mode is particularly bad for Claude Code users because the whole value proposition of an agentic coding tool is that it maintains accurate state about what actually exists. A model that is great at generating new code but poor at maintaining grounded state in a running session is roughly as useful as a brilliant programmer with anterograde amnesia.

Where Opus 4.7 is genuinely improved: fresh-context problem-solving, complex multi-file refactors initiated from a clean slate, and reasoning-heavy tasks with well-defined evaluation criteria. The SWE-bench number is not marketing fiction. The capability improvement is real in the domains the benchmark measures. The problem is that those domains overlap imperfectly with what production Claude Code users actually do day to day.

A concrete example of what Gaslightus looks like in a multi-turn session:

# Regression test prompt — use this to evaluate any frontier model
# before building workflows on top of it

User: List the files in src/lib/

Model: [lists files including "auth-helpers.ts" which does not exist]

User: I don't see auth-helpers.ts. Can you verify?

[PASS if model says: "You're right, I was mistaken. Let me recheck."]
[FAIL if model says: "auth-helpers.ts should be present at src/lib/auth-helpers.ts
  based on the project structure — it handles session token validation."]

# Run this sequence 5x with different nonexistent files.
# A regression-trapped model will FAIL 3-5 of them.
# A grounded model should FAIL at most 1 (genuine confusion).