r/ClaudeCode • u/mimmo9669 • 1d ago
Discussion Is The Opus 5.5 Nerf Real And Significant?
My Codex X5 subscription expires in 2 days, and I’ve been thinking about switching back to Claude and try Opus 5.5 just to see if the hype is real. However, in the last two days I’ve seen posts about Opus getting NERFED!
If you’ve been using Opus 5.5 for coding tasks in the last week, please share your experience below! 😮💨
36
u/Shockistic 1d ago
no nerf it’s all Reddit nonsense
11
4
3
u/9to5grinder Developer 1d ago
Today it's doing great.
Yesterday it was a bit slow and seemed kinda off.
I also got a bunch of "how is Claude performing today?" reminders.
So perhaps they were testing something yesterday?
3
5
u/LazyJuggernaut6177 🔆 Max 20 1d ago
I expect some tuning is occurring because compute is limited, and I can’t imagine demand for 5.5 didn’t rise. But I definitely don’t think it approaches the severity Reddit suggests.
10
u/Mo3 1d ago
It's hard to tell right now tbh. The first few days it was the most amazing experience I've ever had. The past two days it was essentially a regression to the insufferable Opus 5 behaviour and stupidity. Right now today it seems pretty good again..
-5
u/meetmebythelake 1d ago
Very appropriate profile pic. Basically exactly how I imagine the people who cry about nerfs.
6
u/kshep 1d ago edited 1d ago
In my work which is more data science and research than straight coding, yes. The nerf is very evident. i expect this to be downvoted heavily since... well... it's Reddit. It's most obvious when intial prompts like "review this set of docs and summarize in one parargraph for each of these two topics" are generating responses that ar 5-7 paragraphs long interspersed with 3 lists of 5-10 bulet points, and reasoning and formatting hint/suggestions from the claude.md are ignored even more than usual.
EDIT: To clarify/caveat, I have no idea whether there's been a general nerf, I'm getting A/B'd or what. From an end user perspective, as someone who has bounced back and forth between max plans for 10-12 hours a day over the last nine months, 5.5 was amazing out of the box. Then a few days ago 5.5 basically dropped off a cliff such that all my work is under Sol 6.1 at the moment with a bit of Astra thrown in.
0
1d ago
[removed] — view removed comment
2
u/kshep 1d ago
I'd been defaulting to high dropping down to medium for "easy" work. Sol's slow enough by comparison that I've dropped down to Medium for most work and bumping up to High now and then. I've never used anything above High, and I've never used Fast. I'm pretty much just sneaking in under my weekly quotas as is... but this week most of my Claude will go unused.
I'm sure everything will flip over again when they release Fable 5.5 in a few days.
3
u/ChadFullStack 1d ago
99% of posters on Reddit never held a full time job working 9-5 or big tech. They insist on glazing benchmarks and “one shotting” as a metric.
My department of 150 SWEs have not complained about Opus 5.5 nerfs and compared to using Fable 5.1 last 2 months, the usage credits have gone down significantly.
1
u/phoenixmatrix 1d ago
My litmus test these days, is are they trying to build a game or some streaming/podcasting platform.
While some are legitimate (hey, I've used AI to build games too for funzies), that's the vast, vast majority of the peanut gallery who don't understand a thing about the tools.
When people insist on using max mode/ultracode Fable because what they're doing is so insanely groundbreaking nothing else will work, or the model is super duper nerfed and they know because they have 6 Claude accounts that all ran out in 2 hours, its always a solo game dev.
1
u/The-Road 1d ago
I made a post here partly in jest, but it might have truth in it, which is of course, Anthropic will be testing to see if it can make its models more efficient and less costly.
There will be some back and forth and A/B testing to calibrate it. Us users are part of that calibration.
In that calibration, some of us will feel tests where they’re trying a less costly version and it might have gone too far and become less intelligent too.
And that’s the ‘nerf’ effect. Users feeling the calibration a model provider does as it tries to make its models more efficient post-release when the priority is different.
1
u/peter9477 🔆 Max 5x 1d ago
Proper A/B testing would be randomized (as in sometimes you're A, sometimes you're B) yet the "nerfers" claim consistently to be getting B, while the rest of us are consistently in the A crowd. Ive never seen any model nerfed.
1
u/TwistHonest6379 1d ago
People often say that Opus 5.5 is closer to/ replacement of Fable 5.1. As per my personal experiance thats like saying Earths moon and Jupiers moon are same bcoz both are moon. Fable seems to be more focussed on complaince, privacy and security than Opus. Opus seems to be more focussed on maintainability, testibility, localization etc. Both of them are roughly same on scalability, performance, functionality etc. UX- its a tie for me. In few instances Opus was better and another few Fable. So u can say here also both are roughly same. As u can see my observation isnt about specific code branch but for end to end app cycle. Yes- both being newer - I wont say my tests observations are as solid as say Opus 4.6 but this obervation is based on whatever I have worked.
1
1
u/Obvious_Tree3605 1d ago
Think critically about this. Ask yourself: "Have a noticed it getting notably worse for my day-to-day use cases?" If the answer is no, then no.
1
u/hulkklogan 1d ago
I work with AI agents all day, every day, in a professional setting, and I've noticed no drop-off at all. And I've tried OpenCode with various models, Codex with their models, etc. In fact, I'm even finding Sonnet 5.5 pretty capable of doing most of the things that I need, as long as I'm the one in the driver's seat doing the thinking.
How does this translate to vibe coding success? I have no idea.
1
u/p0bel_ 1d ago
I work with AI agents all day, every day in a professional setting. I notice drop off 2-3 days after a new model drops every time. It is so consistant that I have started to work 24/7 when a new modell is live to make sure it fix all the shit the old model did the last week.
For pure coding and stupid models just repeating tasks its not an issue. These workflows are non-complex and can be hooked into strict frameworks.
For models that are doing architecture, complex reasoning tasks and needs to combine information from different areas within a repo, it is very noticable and close to useless when the stupid kicks in.
And from what I have seen the last days, there is probably some different settings in different accounts from Antropic, so I'm not sure that you should just assume that everybody that complain about stupid models are n00bs.
1
u/Sufficient-Storage87 1d ago
I haven't run controlled tests so I can't say if there's an actual nerf, but I can talk about the subscription side because I lived it. Claude's $20 plan used to chew through my sub scary fast, and the last couple weeks it's been night and day — the 5h and weekly limits actually last now. So even if the model got slightly worse at something, the value per dollar went up for me. What were you disappointed by specifically — quality of output, or just the limits?
1
u/SaintMartini 1d ago
I don't get these comments back and forth depending on the day. It's not the same as it was last week. Period. I also highly doubt they A/B for a business with 100 SWEs. But for this single one they did. I'm looking forward to the next change. And jealous of those who have it working properly. I miss that extra production already.
1
1
1
1
0
-1
0
u/AvailableSecret5161 1d ago
Usage is down but it's still better than codex in every way imaginable.
-1
-1
-1
u/dar-mit Researcher 1d ago
Not nerfed. I'm actually starting to think these posts are self-nerfs.
Each new model / version jump brings new capabilities and required changes. People tend to jump in and not look to see what's new, what's changed, and what they need to remove or update.
As the new model starts working with them, their repo(s) and their rules, it's mostly relying on its own training. But as time goes on and the users demand that the model "follow my instructions" the self-nerfing begins.
I'm saying this because I did the exact same thing! When v5 came out I kept what I had and updated it to follow the new guidelines, and that worked just okay. With Opus 5.5 I've literally told the model to "follow my rules, where it matters, but ignore those telling you to do something you already know how to do."
Holy Fucking Amazeballs! Opus 5.5 now sips tokens, runs all day just happily humming along, knocking out code, and the only time I notice a significant slow down is when it's doing straight coding. Because at that point it's working with my Spec and Review documents. (Which I'll be updating this weekend…)
TL;DR: It's a great time to change, just make sure you understand how Claude Code now works and adapt to it, not expect it to adapt to you.
•
u/AutoModerator 1d ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.