Earlier quoted context omitted.
I feel like Anthropic is going down a bad path here with billing things this way. Especially as local LLM continues to develop so fast. I downgraded from my $200 a month plan to my $20 plan and hit limits constantly. I try to use the API access I purchased separately, and it doesn't work with Claude Code (something about the 1 million context requiring extra usage) so I have to use it Continue. Then I get instantly r…
>Especially as local LLM continues to develop so fast. I'm sorry is there anything even close to sonnet, much less opus, that can be run on a 4080? Or 64gb of ram, even slowly?
Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw
671–680 of 928 posts
Re: Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw
#672Re: Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw
#673Re: Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw
#674Claude is a UNIX command line tool with an SDK. Yes there's an interactive mode, but it can be invoked as a normal utility too, and piped to other tools and so on. In that context, I don't understand the difference between a "third party harness" and a shell script. How are they even detecting OpenClaw?
They have terms to not allow `claude -p` used like that. However, people can hide this with the leaked source code. What a funny cat-and-mouse game!
Re: Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw
#675Earlier quoted context omitted.
What you're saying is conceptually true for subscription services in general, but thats not why they are making this change. There's a 5 hour limit and a weekly limit. Those are hard token limits. Everyone on a plan pays for the max set of tokens in that plan. The limits manage capacity. The solution to that isn't a change of ToS, it's adjusting the limits. In other words this is about Anthropic subsidizing their own…
If they bundled together these two radically different usage patterns, either the service would become more expensive or the limits would become a lot tighter, in both cases making Claude Code far less attractive to professional users.
Re: Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw
#676Earlier quoted context omitted.
What you're saying is conceptually true for subscription services in general, but thats not why they are making this change. There's a 5 hour limit and a weekly limit. Those are hard token limits. Everyone on a plan pays for the max set of tokens in that plan. The limits manage capacity. The solution to that isn't a change of ToS, it's adjusting the limits. In other words this is about Anthropic subsidizing their own…
Exactly. Subscriptions are crazy subsidized. So you can’t use OpenClaw, OpenCode, etc. because they take you outside their applications/lock in and their ability to easily monetize in the future.
Re: Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw
#677Re: Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw
#678Claude is a UNIX command line tool with an SDK. Yes there's an interactive mode, but it can be invoked as a normal utility too, and piped to other tools and so on. In that context, I don't understand the difference between a "third party harness" and a shell script. How are they even detecting OpenClaw?
They have terms to not allow `claude -p` used like that. However, people can hide this with the leaked source code. What a funny cat-and-mouse game!
Like what? I legitimately don't understand what is prohibited. Using claude as part of a shell script? Am I only allowed to use claude if a physically type the commands into a terminal via my keyboard? Why even ship `claude -p` at all?
Re: Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw
#679Re: Tell HN: Anthropic no longer allowing Claude Code subscriptions to use OpenClaw
#680Earlier quoted context omitted.
> You are paying to be using that limit some of the time. There are 5 hour windows when you are sleeping and can't use it. There are weekend limits. They could easily structure their limits to enforce that kind of pattern fairly on both human and automated users. They could e.g. force a cooldown period between your daily activity bursts, by decreeing that continued heavy use on a 24h basis would count exponentially m…
Or alternatively just pay based on what you use? I.e. $/tokens.