I have truly no idea what this is all about. OAuth login issues aside (which have been a thing on-and-off for a while now, and I hope they fix soon), Claude's performance and responses have been entirely stable for me for like, forever.
Same for me. I have been max200 for like 10 months, i think my usage is reasonable, and i never seem to get the quality throttling that gets complaints daily. I assume they are targeting certain piggies at the Claude buffet, who then squeal the loudest.
Anthropic is burning more and more dev goodwill
31–35 of 35 posts
Re: Anthropic is burning more and more dev goodwill
#32See https://github.com/anthropics/claude-code/issues/42796
Re: Anthropic is burning more and more dev goodwill
#33Earlier quoted context omitted.
Same for me. I have been max200 for like 10 months, i think my usage is reasonable, and i never seem to get the quality throttling that gets complaints daily. I assume they are targeting certain piggies at the Claude buffet, who then squeal the loudest.
As far as I can tell, the people affected are primarily those using their Claude code tokens for openclaw or similar and burning as many tokens as possible
This isn't a OC yahoo.
Re: Anthropic is burning more and more dev goodwill
#34tl;dr: Dude thinks Anthropic is making claude worse on purpose to cut down on GPU usage and/or increase income. He recommends using Codex instead. This video should have been a text tweet. I'm 3 minutes in and he has done an ad read and shown that Anthropic wasn't kidding about removing the ability for Claude to be used with OpenClaw without paying for additional usage. And now he says he's going into his _actual_ pr…
Re: Anthropic is burning more and more dev goodwill
#35Is Claude code really refusing to do none coding tasks because thats not my experience even as of today and I would have expected those tokens are being accounted for the same way as a Claude.ai chat. Seems like all of this is gripes over blocking openclaw which I just cannot take seriously.
Earlier today I had an agent refuse to integrate a proprietary library until I reassured it there was a signed license agreement with the authors. Otherwise it threatened to "escalate this session to the legal department". First time I've seen prompt injection by header copyright warnings.