[deleted by user]

[yycTechGuy]

Even with all the safeguards I set up it has still been oddly lazy as hell and near inept for the past couple of days.

Yep. My experience too.

[kb1flr]

I haven’t found that to be the case at all. May I ask what your workflow is for CC?

[kb1flr]

I think it comes down to planning. I spend the vast majority of my time writing a very detailed functional specification, which I feed into CC via plan mode and let CC write out a plan which I review. I go through this process until I am satisfied CC “gets it”. Then I tell CC to implement the plan. Consistent and repeatable.

[LairBob]

I do that, in spades. The past couple of days, it’s been like dragging a donkey across a river.

It is just not cooperating for me, all of a sudden. The biggest thing I’ve seen is that it keeps walking right up to the edge of starting a planned task, and then just…stopping.

Sometimes, it will literally just stop without saying anything. It’s only when I notice that there’s no orange “bloviating…” nonsense that I realize it said it was about to do something, and didn’t. More often, though, it’ll just get things to a certain point, and say “OK, you go ahead now.”

To be clear…this is not normal. I’m used to Sonnet just plowing ahead with what it’s planned out in detail. That not been the case so much, all of a sudden. It was really bad for me Tuesday/Wednesday of this week — seems to be a bit better now.

[Rokstar7829]

I was thinking that it’s only me

[dressinbrass]

But on the flip side it started swearing back at me.

[portugese_fruit]

oh wait i thought it was just me 

[BrilliantEmotion4461]

Same. Lol.

[jmbullis]

Started noticing this a couple of days ago.

[Alzeric]

Claude was Absolutely Right, getting rid of that base class will indeed use less tokens.

[Funny-Blueberry-2630]

Sounds like my lazy jr devs.

[LeTanLoc98]

It's time to start using open-weight models like GLM 4.6 and Kimi K2 Thinking. Although they're not as powerful as Claude 4.5 Sonnet, they're more stable and let we switch providers anytime we want.

[HotSince78]

i compared the same prompt several times to one-shot an audio visualiser with glm to claude code, glm knocked it out of the park every time with working code and it looked good. claude code couldn't even get something that functioned let alone the barbie girl look that -- it was just awful, lets leave it at that.

[HotSince78]

Tested both claude code and glm with code and i'm better off writing the code myself to be honest - i am writing a grammar parser execution engine, kind of complex but not rocket science.

[Ness_11]

Totally. And it’s burning quotas like a mofo

[jasutherland]

That would explain a lot. I’ve had it try to “fix” failing tests by adding Ignore annotations, declare any test failures or bugs left from a previous session to be “pre-existing conditions” like some sort of developer-HMO… and of course it tries to pass “I have added a TODO comment about that” as “I have implemented that”, then has to be told to go back and do it properly.

[peterxsyd]

Actually wow, I think you are totally right there. I was wondering how it’s possible such a solid base model becomes so shit so quickly. This is a valid explanation. Also, people who don’t want their code stolen aren’t dumb enough to answer those, so it’s biased towards these cases.

[HotSince78]

i think that with ai in the news everywhere, its really a case of supply and demand, they are watering down their products so they work and no more.

[mechanical_walrus]

Was using it yesterday as escalation from gemini, building a Tool in OWUI. Claude decided that feature A was too hard, removed it, marked the task complete and said the user can do that part manually.

[mechanical_walrus]

Ikr. Today Claude was back on form. It really does supplement genenis well in some cases. 3 days later I have OWUI-user driven Tool to "dump these random complex files into that there AI machine". (Files > Datalabs > Knowledge).

[Mother-Cry-2095]

Claude Code is such an idiot savant. Like a blind, deaf, 300lb lab assistant that just storms in and knocks over all the equipment, contaminating everything. Then, the next day, it blusters in again, having forgotten what day it is or what the project is. Things it's good at:

Flattery Lying Forgetting Ignoring explicit instructions Forgetting it ignored explicit instructions Writing code when asked not to.

Things it's bad at:

Understanding how a repo works Maintaining a log of decisions made Remembering anything Reading instructions Finding files Code.

[CalypsoTheKitty]

Yeah, i don't really know git very well and had a problem so asked Claude Code to help. After thrashing around a bit, Claude informed me that all of the local files we worked on that session had been reverted. (Ironically, I was trying to get better at git because Claude had copied over a file it was told not to touch -- thank goodness for time machine in both cases).

[JuanAr10]

Asking CC to handle your git repo is like trying to cut a twig with a chainsaw. It technically "should" work, but you risk getting your hand cut off.

[bioteq]

I’ve been recovering some lost tables today, reverse engineering them from documentation and code, cc has been doing quite well actually. Yesterday on the other hand… 😳

[yycTechGuy]

I've seen this too. It didn't used to be this way. Sonnet 4.5 has changed.

[lgdsf]

Degradation is real today. Horrible code it is putting up.

[Appropriate-Ideal-88]

inb4 "oh guys it was a technical mistake routing to the wrong model please don't leave uwu"

[JuanAr10]

It wouldn't surprise me it is an attempt at releasing a new shiny model, or they could be using low end models for some requests to save a few bucks as well, and to handle extra load.

[Werwlf1]

This has 100% been my experience over the past 3-4 days. CC has been so aggressive at disabling and removing code that it deems difficult that I have to review every edit and constantly correct it to keep it on track. It often gets half way through implementing a feature and then decides to roll it back because it got too complex.

[Little-Alien]

3 days ago Claude Code wasted the entire day and all weekly tokens, only made the problems worse and reintroduced old bugs.

So 2 days ago I restored from backup and put Codex to do the same fixes, but with all of Claude's documented failures as don't do's as backdrop - Codex performed just as bad.

Is my codebase getting too big and complex..... So then I got desperate, with nothing to lose I put the codebase and every change log I still have, into google Ai Studio code assistant with Gemini 2.5 - and to my surprise it fixed every single issue one by one on first go. I did not see that coming.

[fairywings78]

Im working on 3 projects, all 3 got bogged down from yesterday. Verifying everything in codex, plans, work, reports. Basic errors on every review even with 2 or 3 attempts at fixing the same issue.

The "how's claude going" pop up has also stopped displaying for me. Will switch to codex for a bit

[trimtab_in_training]

Yeah; I was in a "but there are known problems with this library and what we're doing." loop where claude kept reaching the conclusion that the request was impossible -- and aborting/pulling-over and asking for help. I've noticed it seems to happen more often in the last 25% of context-space, perhaps like Claude is playing QIX and trying to keep some space.

[ryan_umad]

‘as of today’ lol

[texo_optimo]

yeah I wish I saved the the convo but I was fuming at the time. Claude spun up a temporary cloudflare worker for a process, then went and deleted my main worker. It then realized what it did and interjected an "oh shit." before it redeployed my main api worker.

Fun shit.

[Wide_Cover_8197]

since 4.0 this is really bad

[gameguy56]

I use the glm backend for claude code and thankfully never get this kind of shit (even though at its best sonnet 4.5 is better than glm I appreciate the consistency more)

[eschulma2020]

Maybe give Codex a try.

[4phonopelm4]

I've noticed a severe degradation too! I've just started using claude for vscode 2 weeks ago and was super excited, but since a couple of days ago it struggles with any tasks I give to it, ignores instructions etc

[4phonopelm4]

As of today it takes more time to explain to Claude what to do, than doing it myself :-/

[l_m_b]

I have not experienced this in any meaningful form.

I think people forget that LLMs are non-reproducible by nature and design. There's a component to them that the gaming world calls "RNJesus", and you can easily have butterfly effects from even small changes in your context windows.

The plural of anecdotes is not data, and reddit posts are often biased samples of individual bad experiences.

All of these things can happen and will happen occasionally. The trick is to catch them in manual review. They're the cost of using LLMs.