I take your point, the way I used “abuse” there probably carries more charge than I’d meant it to. It’s a totally valid way to use the technology, it’s “abusive” only of the subscription program. And I agree: Anthropic clearly want people to industrialize and automate usage. But that’s not what the subscription product is for. Use all the loops you want, burn all the tokens you want—just pay what they cost.
> is there a way to use the quota that's not 'abuse'?
I think my answer is “no.” In that I’ve never thought of the limits as “quotas,” and I don’t think I’ve heard Anthropic speak of them that way. Quotas are to be used up, while limits are to signal that what you’re doing is outside the envelope of acceptable use. Quotas are to be met, limits are to be avoided.
I interpret the intention of the subscription, like a membership at a makerspace, to be to allow novices to experiment with stuff, to take on personal-scale projects, to allow them to learn without having to understand the tool’s economics upfront. To play without fear of expensive mistakes.
And, like the makerspace, it can only offer generous limits to the extent that most of us rarely bump up against them. If you’re doing production runs in the makerspace, you’re crowding out the other members, and something’s gotta give.
To the extent that we do bump against the limits during “ordinary” use—and we do with Claude Code, especially those of us around here—it’s really frustrating. The limits need to rise in order for it to remain attractive to casual users like me, the economics still need to add up for the subscription program as a whole, and part of that is separating out what patterns of use belong under a different regime.
If these harnesses or OpenClaws or whatever stop making sense as soon as they have to pay their actual costs, then that’s a pretty good sign they’re abusing the spirit of the subscription.
But Anthropic seem more than happy to service those uses via the API or metered usage, and even to sweeten the deal with more reliable access and bulk discounts. I certainly wouldn’t characterize the same automated usage as “abuse” via that channel.
>>I take your point, the way I used “abuse” there probably carries more charge than I’d meant it to.
Fair enough.
>> But that’s not what the subscription product is for.
This was the point I was trying to make - I pay for XX tokens/usage. But somehow using them all is 'taking advantage' ?
BTW - I'm actually not complaining about the limits - I probably only use half my tokens on average week. I'm just annoyed at having to jump thru hoops if I want to try something 'API' oriented. For me, AI is still the new shiny - I try all different sorts of things learning/playing. There was an article posted today about writing agent harnesses. That could be interesting - maybe I want to try my hand at it. But then I've got to mess around/pay extra to _try_ something I that my subscription already easily covers.
[added:] >>to take on personal-scale projects, to allow them to learn without having to understand the tool’s economics upfront. To play without fear of expensive mistakes.
This is exactly what I'm trying to do - however, as soon as you want to try anything 'API' oriented, the 'fear of expensive mistakes' comes right back.