[flagged]
I'm hoping with this change we see the rate limits start to not be as rough.
391–400 of 928 posts
[flagged]
I'm hoping with this change we see the rate limits start to not be as rough.
Earlier quoted context omitted.
Well earnest here just means using Claude code directly or the Claude app. Both that just happen to support using tokens while you sleep!
Defining earnest (placeholder word btw) is the hard part of the trade-off, though. When your least automated, most interactive users are competing for capacity with fully-automated tools, let's say, you're forced to define some sort of periphery between these groups. OpenClaw is a self-directed, automated loop that sits on a server. It's wowing its owner by shitposting on moltbook and doing any number of crazy storie…
I'm sorry but this framing just doesnt make sense.
I suspect people are misdiagnosing the root cause of why Anthropic is doing this a bit. I don't think this is particularly about the financial impact of people using OpenClaw - they can adjust the amount of tokens in a subscription quite easily. I think the root cause is that Anthropic is capacity constrained so is having to make choices about the customers they want to serve and have chosen people who use Claude Cod…
I'm at large company and pretty much everyone has settled on opus or sonnet 4.6. We would absolutely not allow something like OpenClaw on our network so your point kinda fits here where, if capacity is constrained, then by setting focus away from OpenClaw you're essentially prioritising the enterprise clients. Just spitballing of course
I doubt they actually want to do this.
They clearly see having a wide set of paying customers as valuable (otherwise they'd just raise prices) but if you are stuck having to make hard choice then I can see the attraction of this approach.
Earlier quoted context omitted.
I don't understand this perspective. I can't imaging a point where I won't want to ask "what's the weather like?" "please turn off the lights" "what is the airspeed of an unladen swallow?" likewise chatting through directing it to build something or solve a problem, voice or typing will each have their place. And video calling did take off, plenty of people use facetime and almost everybody working in an office uses…
> I can't imaging a point where I won't want to ask "what's the weather like?" "please turn off the lights" To help with understanding that perspective, I cannot imagine a scenario where I would ask a device connected to the internet to turn off the lights. I literally never wanted this. A physical switch is a 100% non negotiable for me. I feel the same way about non-mechanical car doors. Perhaps due to that outlook…
Earlier quoted context omitted.
If people are finding new ways to use AI, they should change how they bill. Banning third party harnesses is bad for a lot of reasons - it looks like they're trying to force people to use their software. Strategically it might make sense - gives them a tiny moat if their models ever slip - but it discourages the breakneck pace of innovation and the long term effect is that their customers (largely highly skilled with…
They don’t need to change how they bill. Your subscription is for Claude app/code. Otherwise you pay per token. It’s always been this way.
If the actual concern is use pattern, enforce that directly. What we have instead is metered usage + behavioral restrictions + product fragmentation across three separate offerings.
That's not a clean billing philosophy, it's layers of control stacked on top of each other with no coherent logic tying them together.
If subscriptions are for humans and API is for automation, fine. But then don't meter the human product arbitrarily and don't sell a subscription tier for automation while also restricting automation. Pick a lane.
Earlier quoted context omitted.
Defining earnest (placeholder word btw) is the hard part of the trade-off, though. When your least automated, most interactive users are competing for capacity with fully-automated tools, let's say, you're forced to define some sort of periphery between these groups. OpenClaw is a self-directed, automated loop that sits on a server. It's wowing its owner by shitposting on moltbook and doing any number of crazy storie…
Claude code has /loop. Claude app has scheduled tasks. The leaked source has a proactive mode. I'm sorry but this framing just doesnt make sense.
In that context, I don't understand the difference between a "third party harness" and a shell script.
How are they even detecting OpenClaw?
Earlier quoted context omitted.
Those yottabytes of VRAM are also consuming electricity constantly.
The difference being that an LLM request is not an operating system. Since they're compartmentalized and ephemeral, you can very easily distribute requests among your available hardware so that you can switch off machines during periods of low activity.
Earlier quoted context omitted.
>They have to be honest about what they can offer for $200 Their expectation must have been a human using the service at a human capacity. This is different from an automated agent orchestrating a ton of different agents at the same time doing a lot of things. There is a difference.
If people are finding new ways to use AI, they should change how they bill. Banning third party harnesses is bad for a lot of reasons - it looks like they're trying to force people to use their software. Strategically it might make sense - gives them a tiny moat if their models ever slip - but it discourages the breakneck pace of innovation and the long term effect is that their customers (largely highly skilled with…