AI Newsletter

Claude Opus 4.7 is here. The benchmarks look great. The community is skeptical anyway.

Anthropic just shipped Claude Opus 4.7. Benchmark numbers are up substantially. Developer reaction is   … not quite the usual launch day excitement.

AI AI Excellence

Overview

The headline claims: long-running tasks handled with more rigor, more precise instruction-following, and output self-verification before reporting back. Vision is now at three times the previous resolution. On the API side, a new xhigh effort level sits between high and max, and task budgets in beta give you cost controls across longer runs. For Claude Code users, there is a new /ultrareview command and auto mode now extends to Max subscribers.

On paper, that is a meaningful upgrade. The third-party Vals Index put Opus 4.7 at 71.4%, a jump from the previous best of 67.7%, and it ranked first on Vibe Code Bench, SWE-Bench, Terminal Bench 2, and several others. Those are not trivial margins.

The Benchmarks Case

One thing Anthropic did right here: they did not hide the gaps. The published benchmark table shows Opus 4.7 losing to Opus 4.6 and GPT-5.4 on certain tasks. One reply on the announcement thread noted this directly, saying it made the wins feel more credible rather than cherry-picked. That is a fair read.

The self-verification feature is worth watching. If it holds up in real use, it directly addresses one of the most common frustrations from the last few weeks: Claude completing a task, reporting success, and being wrong. “Less ‘here is a guess’ and more ‘here is the answer, checked twice'” is exactly the direction the tool needs to move.

The Community’s Take

The reply section on the announcement tells a different story from the benchmarks. A few representative takes:

“T minus 30 days until it’s nerfed.”

@OhMyKaush

“Classic move. You deliberately lowballed Opus 4.6’s performance in this comparison just to make 4.7 look like a massive leap.”

@Agastya79646

“4.7 currently is worse than the 4.6 I had a week ago or the 4.5 I had this morning that you just removed. Idk what y’all are doing but this ain’t it.”

@GhostofCrockett

“So it’s mostly upgraded for coding and agentic use and it actually got downgraded in other things. Well this is new for sure.”

@OliwierMako

Reddit’s r/ClaudeAI thread ran in the same direction. The auto-generated TL;DR from the thread captures the mood well: “The overwhelming consensus is that Opus 4.6 was degraded for the past few weeks to make 4.7 seem like a bigger upgrade. Many users are convinced 4.7 is just a rebranded version of what 4.6 used to be.” The top-voted comment in the thread was simply: “4.6 started sucking for last 2 weeks, is this the strategy?”

One concrete concern worth separating from the sentiment: Opus 4.7 ships with a new tokenizer that maps the same input to roughly 1.0–1.35× more tokens depending on content type. That is not a vibe complaint. For users already bumping usage limits with Opus, that is a practical cost increase on top of the existing pricing.

These are early impressions from day one, which are always noisy. But the pattern is consistent with what we covered in issue two: users who watched Opus 4.6 degrade over the past several weeks are not coming to this launch in a neutral state. When trust has slipped, benchmark charts do not automatically restore it.

My Take

The cynical read is that Opus 4.7 is pre-nerf Opus 4.6 repackaged with new version numbers. There is no evidence for that beyond timing and frustration, but that theory is going to have legs for a while because it is hard to falsify quickly, and the timing is genuinely suspicious.

The more charitable read: Anthropic shipped a real capability jump, the benchmarks are credible enough to take seriously, and the community’s reaction says more about eroded trust than about the model itself.

There is also a third read that is less dramatic than either of those: Anthropic ramped up 4.7 infrastructure over the past few weeks, and that reallocation of compute is what degraded 4.6, not a deliberate decision to make the old model look worse before the launch. If that is what happened, 4.7 could be genuinely better without anyone having sandbagged anything intentionally. It is the most boring explanation, which also makes it the most plausible one.

I genuinely hope 4.7 performs better than the degraded 4.6 we have been dealing with. If it turns out to match or exceed pre-nerf 4.6 performance, that is worth saying clearly even if the path to get there was messy. If it turns out to be a meaningful step forward beyond that, even better.

But we do not know yet. The model launched yesterday. What we are hearing now is not a verdict, it is noise. Real signal comes from repeated use on real work over the next week or two. That is what we should be collecting.

What We Are Watching

The SWE benchmark comparison I mentioned in issue two is now more relevant than ever. Opus 4.7 is live, so the test scope expands to include it alongside Sonnet 4.6, Opus 4.6 and GPT-5.4. The questions I want answered:

· Does 4.7 read repos before editing, or does it still jump straight to changes?

· Does self-verification actually reduce hallucinated file paths and wrong API calls, or is it marketing copy?

· Does the prompt churn feel like pre-nerf 4.6, post-nerf 4.6, or something different from both?

· Does it hold up over multi-session work, or does quality drift?

If you are using Opus 4.7 this week, those are the things worth paying attention to. Not whether the first response felt sharp, but whether it stays that way across a full session on a real task.

Sources → Anthropic release post  ·  r/ClaudeAI thread  ·  X announcement
GET STARTED

Tell us what you want to build.

Whether it’s a quick question or a detailed brief — we’d love to hear about it.

  • Honest assessment of whether we're the right fit
  • Fixed pricing, no hidden costs
  • 10+ years of trusted delivery
No sales pressure.
No lengthy process.
Just an honest conversation about technology.








    We'll use these details only to reply about your project. See our privacy policy.

    Thank you for contacting us!

    We'll be in touch with you shortly.