Has anyone figured out getting Claude Code to work with a locally installed (e.g via ollama) or a self-hosted LLM already?
Claude Code weekly rate limits
721–724 of 724 posts
Re: Claude Code weekly rate limits
#722Earlier quoted context omitted.
I don't think this counts as a "dark pattern". The reality is that these services are resource constrained, so they are trying to build in resource limits that are as fair as possible and prevent people from gaming the system.
Besides the click mazes to unsubscribe I’m struggling to think of a darker pattern than having usage limits but not showing usage. The dark pattern isn’t the usage limit. It’s the lack of information about current and remaining usage.
[dead]
Re: Claude Code weekly rate limits
#723Earlier quoted context omitted.
Internet and SMS used to be expensive and metered until they weren't thanks to technological advances and expanded use. I think LLMs will follow the same path, maybe on a shorter timespan.
Isn't it the exact opposite? No one is making profit yet, it is a mad dash to monopolize the market, it has to get more expensive to ever turn profit, so the screws will turn
Yes! I agree completely. They’ve not even turned on the money faucets yet. These prices are likely just to hook users on the product, and will be more comparable to paying something that compares, but favourably, to minimum wage per hour in the future. Not implying a nefarious scheme, I just think that’s how the economics of it will pan out.
Re: Claude Code weekly rate limits
#724Earlier quoted context omitted.
As a $20 month user, I can tell you in my experience it's "refactoring" jobs that really smash through those tokens quickly. If you do a "write a component that does this" kinda thing, you can use the $20 plan almost an unlimited amount of time. If you are doing "find all instances of ComponentFoo, change to ComponentBar, refactor each screen for correct usage of ComponentBar" kinda things, it's going to grep through…
> If you are doing "find all instances of ComponentFoo, change to ComponentBar, refactor each screen for correct usage of ComponentBar" kinda things, it's going to grep through your code, find multiple files, read all of them into context and start making changes one by one and/or spin up a subagent to do it. You'll be rate limited pretty quick doing things that way. Huh?? grep and sed do this for free ; you don't ne…
For sure, Claude Code specifically has a grep and glob tool (as well as access to bash). The LLM will decide to use those tools to find files, then once it has found matches to what it's looking for, it reads those files into its context. It will then decide if it indeed was a successful match and start working on that file. There's a lot of times it finds a match using grep, reads that into its context and then decides "no, that's not what I was actually looking for..." and moves on.
Unlike some other AI coding IDEs, Claude Code doesn't either keep your entire codebase in context, or use some sort of vector representation and vector search of your code. It basically uses grep to find a keyword it's looking for then reads the file (it can also just read a few lines of a file too) into its context.
It seems to be the "magic" of Claude Code..it's very UNIX like, uses existing tools to do what it needs to do instead of trying to re-invent the wheel, so to speak.