The Sonnet usage does not really look limited at 240-480 hours per week (a week has 168 hours in it).

Opus at 24-40 looks pretty good too. A little hard to believe they aren't losing a bunch of money still if you're using those limits tbh.

▲

clharman 5 days ago | parent | next [-]

Pretty sure they are still losing money on it, which is great for us. And these limits wouldn't even be happening if there weren't people bragging about having their CC running constantly for 30 hours writing 2 million lines of (doubtless bad) code. And sharing accounts to try to get even MORE usage. It's all that swarm guy tbh and he's proud of it.

▲

j45 5 days ago | parent | prev | next [-]

The calculation of hours is a little tough to imagine sometimes, is it the inference time itself, or the period of time used? Is there an average token cost per hour of use (average or explicit?)

▲

Filligree 4 days ago | parent [-]

It had better be inference time; I regularly have Claude call out to tools that take hours to run.

	▲	j45 3 days ago \| parent [-]
		Yeah, I hope so too, but the silence might be a "it depends"

▲

wrs 5 days ago | parent | prev [-]

You can run multiple instances of Claude Code at the same time.

	▲	furyofantares 5 days ago \| parent [-]
		I know, I do it all the time! I wasn't calling out 240 hours as being impossible to hit in 168 hour weeks. I suppose "does not really look limited" could be read multiple ways - I did not mean it's literally unlimited, just that it doesn't look very limited. You can make your own comparison to however many hours you usually spend working in a week and how many sessions you have active on average during that time.