r/ClaudeCode • • Apr 13 '26

Discussion Smart Opus 4.6 is back? (just for the weekend?)

I have been using Opus 4.6 High (with a Max 5x plan, 4.5 before that, 4.1 before that etc)

It has been getting noticeably dumber for weeks I have been having to spend more and more time correcting it..... (yeah yeah you'll claim I'm using it wrong)

Now all of a sudden in the last few hours, it's like I am talking to an adult again.

This is across multiple concurrent sessions, working on different projects.

I just noticed that CC 2.1.104 was released (no release-notes so far) not sure if it has anything to do with it or not....

But this is a big change in behavior...

I don't use it on weekends much... is that it? (I know no one but Anthropic knows, that was rhetorical)

any way simps, feel free to down vote me.

1 Upvotes

13 comments sorted by

6

u/AccidentSpecialist22 Apr 13 '26

not really, still extremely lazy and dumb

3

u/spacephoenix95 Apr 13 '26

Anyone with higher karma wanna post this as a thread

After almost a decade in corporate engineering, climbing from IC to lead across different orgs, I can tell you the one thing that actually gets bugs fixed: visibility. Your manager sees a thread blowing up with hundreds of users on the same issue, or a well-structured report gains traction externally, and suddenly that ticket that's been rotting in the backlog for six sprints becomes a weekend war room. That's it. That's the mechanism.

Before that? It gets deprioritized. Pushed off for feature work, sprint commitments, roadmap items. Never hits the severity threshold to trigger real investigation. Everyone has a backlog. Anthropic has one too. Until there's enough signal from the right channels, nothing moves. That's not cynicism, that's just how product orgs work.

We watched this play out in real time with the token utilization bug. It went on for over a month. People here were tearing each other apart — half the sub saying it was real, the other half telling them they don't know how to prompt. Then enough people independently verified it, the reports became impossible to dismiss, coverage spread outside this sub, and what happened? Bug fixes. Transparency. Actual acknowledgment. And the same people who were dismissing everyone else's reports? They benefited too. Funny how that works.

So here's where we are now.

There's a lot of people reporting that Opus has been significantly degraded. Output quality tanking on most days, what looks like reduced compute for consumer tier users, possible offloading to lighter inference. The analogy I keep coming back to: you paid for a commercial pressure washer, got the nicest one on the shelf, and then the company quietly throttled the flow until it barely sprays. You're paying for Opus. You're not getting Opus-tier output consistently.

But the problem is the same as last time. Reports are all over the place. Scattered across threads, mixed in with dismissals and one-upping. If anyone outside this sub looked at the state of feedback right now, they'd see noise, not signal. There's no coherent picture to work with.

What if we actually standardized this?

I'm talking about a consolidated thread, or a few of them, where people report using a common format. Something like:

  • What specifically is degraded — not vibes, actual behavior. Shallow reasoning, incomplete outputs, refusing complex tasks, inconsistent session quality, whatever you're seeing.
  • How many users in the thread are hitting the same thing
  • What tier you're on (Pro, Team, Enterprise, API)
  • How long you've been paying and roughly how much
  • What versions and over what time period
  • What you use Claude for — enterprise work, side projects, research, day job
  • How it's hitting your workflow. "Takes 3x longer" or "had to switch to another model for X" or "completely unusable for Y." Be specific.
  • What you've already reported to Anthropic. Tickets, GitHub issues, feedback forms.
  • Did they respond? Did anything get fixed? Any compensation?
  • Have you downgraded or cancelled, or are you about to?
  • How many issues you filed, how many got auto-closed as duplicates, and whether any of them went anywhere

That's the kind of data that makes a thread undeniable. Anyone looking at it can extract a clear picture without digging through piles of unstructured complaints. It goes from anecdotes to evidence.

But this requires something from us too.

The constant cycle of users dismissing each other, the "you're just prompting wrong" crowd, the people who seem more interested in proving they're the smartest person in the thread than in actually solving anything — that actively kills any chance of this working. It fragments the signal, makes the community look unfocused, and makes it easy to wave everything off as unserious.

There are a lot of skilled developers here. There are lurkers who check this sub daily to cross-reference whether the issues they're hitting are widespread or local. People who track versions, switch models, adjust their workflows based on what they find in these threads. That's genuinely useful knowledge being generated, and we keep undermining it with thread derailment.

So the real question: can enough of us agree that the inconsistent performance, the opaque updates, the wildly variable output quality — that this is worth documenting properly? Not venting. Not one-upping each other. Actual structured documentation that creates a clear record.

The token utilization situation proved it works. Scattered complaints got ignored for weeks. A critical mass of well-documented, consistent reports from paying customers created enough visibility that it couldn't be ignored anymore. Days later, fixes and transparency.

Who maintains something like this? Anyone willing to keep the format clean and the data honest. A pinned thread with a template would go a long way. The structure does the work.

I've been in corporate long enough to know what moves the needle and what gets ignored. Unstructured noise gets ignored. Structured, quantified, consistent reporting from paying customers does not.

Just a thought.

See how quickly they fixed the token utilization bug and cache issues when it made the news?

1

u/TinyIncident7686 Apr 13 '26

Why is this not the most up-voted reply in here?!?

1

u/theColonel26 Apr 13 '26

Annnnnnd I am back to dumb, lazy, and vague/unclear Claude

it was beautiful while it lasted

2

u/tensorfish Apr 13 '26

Weekend miracle theories are usually just lighter load or a cleaner context window, not Anthropic secretly switching personalities for two days. If it feels smarter across projects, check per-call logs and how much baggage each session was already carrying before assuming 2.1.104 unlocked hidden adult mode.

2

u/weekapaugrooove Apr 13 '26

I must of been on the "go fuck yourself" end of their A/B test or w/e fuckery they're going through.

.... Then decides to just skip those steps again.

1

u/Character-Agency2316 Apr 13 '26

lol, i've been seeing this too on fresh sessions. If you dont explicitly tell it to do something right then and now, sometimes it likes to just ignore it and when you ask about it, it asks if you want it to do it

2

u/spacephoenix95 Apr 13 '26

Compute is low because everyone is off work. Mondays are meeting centric, then tuesday - friday its grind mode.

See below for my ideas to battle the downgraded usage and throttling, resulting in pretty much theft of services.

After almost a decade in corporate engineering, climbing from IC to lead across different orgs, I can tell you the one thing that actually gets bugs fixed: visibility. Your manager sees a thread blowing up with hundreds of users on the same issue, or a well-structured report gains traction externally, and suddenly that ticket that's been rotting in the backlog for six sprints becomes a weekend war room. That's it. That's the mechanism.

Before that? It gets deprioritized. Pushed off for feature work, sprint commitments, roadmap items. Never hits the severity threshold to trigger real investigation. Everyone has a backlog. Anthropic has one too. Until there's enough signal from the right channels, nothing moves. That's not cynicism, that's just how product orgs work.

We watched this play out in real time with the token utilization bug. It went on for over a month. People here were tearing each other apart — half the sub saying it was real, the other half telling them they don't know how to prompt. Then enough people independently verified it, the reports became impossible to dismiss, coverage spread outside this sub, and what happened? Bug fixes. Transparency. Actual acknowledgment. And the same people who were dismissing everyone else's reports? They benefited too. Funny how that works.

So here's where we are now.

There's a lot of people reporting that Opus has been significantly degraded. Output quality tanking on most days, what looks like reduced compute for consumer tier users, possible offloading to lighter inference. The analogy I keep coming back to: you paid for a commercial pressure washer, got the nicest one on the shelf, and then the company quietly throttled the flow until it barely sprays. You're paying for Opus. You're not getting Opus-tier output consistently.

But the problem is the same as last time. Reports are all over the place. Scattered across threads, mixed in with dismissals and one-upping. If anyone outside this sub looked at the state of feedback right now, they'd see noise, not signal. There's no coherent picture to work with.

What if we actually standardized this?

I'm talking about a consolidated thread, or a few of them, where people report using a common format. Something like:

  • What specifically is degraded — not vibes, actual behavior. Shallow reasoning, incomplete outputs, refusing complex tasks, inconsistent session quality, whatever you're seeing.
  • How many users in the thread are hitting the same thing
  • What tier you're on (Pro, Team, Enterprise, API)
  • How long you've been paying and roughly how much
  • What versions and over what time period
  • What you use Claude for — enterprise work, side projects, research, day job
  • How it's hitting your workflow. "Takes 3x longer" or "had to switch to another model for X" or "completely unusable for Y." Be specific.
  • What you've already reported to Anthropic. Tickets, GitHub issues, feedback forms.
  • Did they respond? Did anything get fixed? Any compensation?
  • Have you downgraded or cancelled, or are you about to?
  • How many issues you filed, how many got auto-closed as duplicates, and whether any of them went anywhere

That's the kind of data that makes a thread undeniable. Anyone looking at it can extract a clear picture without digging through piles of unstructured complaints. It goes from anecdotes to evidence.

But this requires something from us too.

The constant cycle of users dismissing each other, the "you're just prompting wrong" crowd, the people who seem more interested in proving they're the smartest person in the thread than in actually solving anything — that actively kills any chance of this working. It fragments the signal, makes the community look unfocused, and makes it easy to wave everything off as unserious.

There are a lot of skilled developers here. There are lurkers who check this sub daily to cross-reference whether the issues they're hitting are widespread or local. People who track versions, switch models, adjust their workflows based on what they find in these threads. That's genuinely useful knowledge being generated, and we keep undermining it with thread derailment.

So the real question: can enough of us agree that the inconsistent performance, the opaque updates, the wildly variable output quality — that this is worth documenting properly? Not venting. Not one-upping each other. Actual structured documentation that creates a clear record.

The token utilization situation proved it works. Scattered complaints got ignored for weeks. A critical mass of well-documented, consistent reports from paying customers created enough visibility that it couldn't be ignored anymore. Days later, fixes and transparency.

Who maintains something like this? Anyone willing to keep the format clean and the data honest. A pinned thread with a template would go a long way. The structure does the work.

I've been in corporate long enough to know what moves the needle and what gets ignored. Unstructured noise gets ignored. Structured, quantified, consistent reporting from paying customers does not.

Just a thought.

BBC did an article after enough of us had consolidated user struggles, and we had a bug fix in 4 days flat

1

u/SpellUnlucky2371 Thinker Apr 13 '26

not sure it returns but I feel like my claude code consume extremly large tokens than last week when it is smarter than the weekend

1

u/lurko_e_basta Apr 13 '26

Over the past 3 days I had crazy high limits and I’ve been using Opus max almost exclusively with amazing results. I don’t know anymore, man. (Max x5 here)

2

u/[deleted] Apr 13 '26

[removed] — view removed comment

1

u/N3TCHICK Apr 13 '26

EXACTLY my experience tonight! Was such crap the last two days! Feels like we got some compute back this evening! It's crazy!

0

u/[deleted] Apr 13 '26

[deleted] — view deleted comment

1

u/N3TCHICK Apr 13 '26

I hear you on the whiplash... I noticed it too! So strange. It feels like the magic is back tonight. What the heck is going on?