Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code users hitting usage limits 'way faster than expected'

theregister.com

Post reply on HN
Print view View original

91–100 of 245 posts

Re: Claude Code users hitting usage limits 'way faster than expected'

#91

Post by mook »

dinakernel wrote: post #38

This turned out to be a bug. https://x.com/om_patel5/status/2038754906715066444?s=20 One reddit user reverse engineered the binary and found that it was a cache invalidation issue. They are doing some hidden string replacement if the claude code conversation talks about billing or tokens. Looks like that invalidates the cache at that point. If that string appears anywhere in the conversation history, I think the star…

That is a summary and a picture of https://old.reddit.com/r/ClaudeAI/comments/1s7mkn3/psa_claud... it looks like?

Re: Claude Code users hitting usage limits 'way faster than expected'

#92

Post by windward »

bitwize wrote: post #63
jorvi wrote: post #29

Earlier quoted context omitted.

For a second I hoped you were gonna comment on how LLMs are going to rot out our skillset and our brains. Like some people already complaining they "have to think" when ChatGPT or Claude or Grok is down. Oh well.

AI will totally rot our brains, just like television, video games, and the internet all did before.

Do you feel that television, video games and the internet had a negligible impact on our culture?

Re: Claude Code users hitting usage limits 'way faster than expected'

#93

Post by dinakernel »

TazeTSchnitzel wrote: post #58
dinakernel wrote: post #38

This turned out to be a bug. https://x.com/om_patel5/status/2038754906715066444?s=20 One reddit user reverse engineered the binary and found that it was a cache invalidation issue. They are doing some hidden string replacement if the claude code conversation talks about billing or tokens. Looks like that invalidates the cache at that point. If that string appears anywhere in the conversation history, I think the star…

That bug would only affect a conversation where that magic string is mentioned, which shouldn't be common.

I guess so - but for people working on billing section of a project or even if they include things like - add billing capability etc in Claude MD - it might be an issue, I think

Re: Claude Code users hitting usage limits 'way faster than expected'

#97

Post by devmor »

JambalayaJimbo wrote: post #89
pxtail wrote: post #53

Recently after noticing how quickly limits are consumed and reading others complaints about same issue on reddit I was wondering how much about this is real error or bug hidden somewhere and how much it's about testing what threshold of constraining limits will be tolerated without cancelling accounts. Eventually, in case of "shit hits the fan" situation it can be always dismissed by waving hands and apologizing (or…

Once you get used to using claude as an abstraction layer you start getting pretty reckless with it. My organization has the concept of "premium models" where our limits reset every month. I hit my limit pretty quickly last month because I was burning tokens doing things that would have been a simple bash loop in the past - all because I was used to interfacing with Claude at the chat layer for all my automation need…

This is a real danger that I think a lot of people will run into as prices go up more and more in the future.

Completely outside of the productivity debate, offloading cognitive tasks to LLMs leaves you less practiced in them and less ready to do them when the LLM isn't available. When you have to delegate only certain tasks to the LLM for financial reasons, you may find yourself very frustrated.

Re: Claude Code users hitting usage limits 'way faster than expected'

#98

Post by arvid-lind »

replwoacause wrote: post #57
dinakernel wrote: post #38

This turned out to be a bug. https://x.com/om_patel5/status/2038754906715066444?s=20 One reddit user reverse engineered the binary and found that it was a cache invalidation issue. They are doing some hidden string replacement if the claude code conversation talks about billing or tokens. Looks like that invalidates the cache at that point. If that string appears anywhere in the conversation history, I think the star…

Nothing devious, but is Anthropic crediting users? In a sense, this is _like_ stealing from your customer, if they paid for something they never got.

Not seeing any quota returned on my Pro account. My weekly usage went up to 20% in about one hour yesterday before I panicked and stopped the task. It was outside of the prime hours too which are supposed to run up your quota at a slower rate.

Re: Claude Code users hitting usage limits 'way faster than expected'

#99

Post by kakugawa »

xnx wrote: post #18
jdefr89 wrote: post #14

Over reliance on LLMs is going to become such a disaster in a way no one would have thought possible. Not sure exactly what, who, when, or where.. Just that having your entire product or repo dependent on a single entity is going to lead to some bad times…

> on a single entity Contrary to the popular opinion here, there are other services beyond Claude Code. These usage limits might even prompt (har har) people to notice that Gemini is cheaper and often better.

gemini-cli has not been useable for weeks. The API endpoint it uses for subscription users is so heavily rate-limited that the CLI is non-functional. There are many reports of this issue on Github. [1]

1/ https://github.com/google-gemini/gemini-cli/issues?q=is%3Ais...

Re: Claude Code users hitting usage limits 'way faster than expected'

#100

Post by novaleaf »

dinakernel wrote: post #38

This turned out to be a bug. https://x.com/om_patel5/status/2038754906715066444?s=20 One reddit user reverse engineered the binary and found that it was a cache invalidation issue. They are doing some hidden string replacement if the claude code conversation talks about billing or tokens. Looks like that invalidates the cache at that point. If that string appears anywhere in the conversation history, I think the star…

your linked bug is a cherry pick of the worst case scenario for the first request after a resume.

While it should be fixed, this isn't the same usage issue everyone is complaining about.

Post reply on HN