I love Claude Code, but Anthropic’s recent messaging is all over the map.

1- “More throughput” on the API, but stealth caps in the UI - On Jun 19 Anthropic told devs the API now supports higher per-minute throughput and larger batch sizes, touting this as proof the underlying infra is scaling. Yay!?? - A week later they roll out weekly hard stops on the $100/$200 “Max” plans — affecting up to 5 % of all users by their own admission.

Those two signals don’t reconcile. If capacity really went up, why the new choke point? I keep getting this odd visceral reaction/anticipation that each time they announce something good, we are gonna get whacked on an existing use case.

2- Sub-agents encourage 24x7 workflows, then get punished… The Sub-agent feature docs literally showcase spawning parallel tasks that run unattended. Now the same behavior is cited as “advanced usage … impacting system capacity.”

You can’t market “let Claude handle everything in the background” and then blame users who do exactly that. You’re holding it wrong?

3 Opaqueness forces rationing (the other poster comments re: rationing vs hoarding, I can’t reconcile it being hoarding since its use it or lose it.)

There’s still no real-time meter inside Claude/CC, only a vague icon that turns red near 50%. Power users end up rationing queries because hitting the weekly wall means a seven day timeout. Thats a dark dark pattern if I’ve seen one, id think not appropriate for developer tooling. (CCusage is a helpful tool that shouldn’t be needed!)

The, you’re holding it wrong, seems so bizarre to me meanwhile all of the other signaling is about more usage, more use cases, more dependency.

▲

nojs 4 days ago | parent | next [-]

> 2- Sub-agents encourage 24x7 workflows, then get punished… The Sub-agent feature docs literally showcase spawning parallel tasks that run unattended.

Yeah, the new sub-agents feature (which is great) is effectively unusable with the current rate limits.

▲

Inufu 4 days ago | parent | prev [-]

You can use Claude Code with your own API key if you want to use more tokens than included in the Pro / Max plans.

	▲	social_quotient 3 days ago \| parent [-]
		Yeah I get that, I’m not “stuck” it’s that I don’t think the comms make sense and it’s troubling none of these teams have figured out a pricing model that isn’t a rug pull. If all of these ai llm coders were priced right, they would be out of the hands of many of the operators that are not dependent users. It’s got a bait and switch feel to it. I’ll deal with it. It’s a good product, I just feel like we deserve better and that these guys are smarter than this. Can you imagine if AWS pulled half of these tricks with cloud services as a subscription not tethered to usage? They wait for you to move all of your infrastructure to them (to the detriment of their competitors) and then … oh we figured out we can’t do business like this, we need to charge based on XYZ… we are all adults and it’s our job to deal with it or move on but… something doesn’t smell right and that’s the problem.