[sevenseacat]

I'm in the boat of wondering how so many people run into session limits so often. I have never hit one, except once when Claude Design came out and I had fun generating a bunch of random things to see what it could do (not with the intent of actually using any of the generated designs/code, because it all sucked).

[linsomniac]

I'm using the $200/mo Claude, and I'll often hit the 5 hour limit, but last week was the first or second time I've hit the week limit. I run pretty much everything on "/effort max" because I've had good results, and I've had plenty of quota left usually, and I want to worry less about "am I getting the best results".

Fable, for the few days I had it, would eat through tokens pretty quickly, largely because it tended to work much more on its own. I could give it a task and after asking a few questions it would go off and work for 4-6 hours and be done.

I also run a lot of experiments. I'm trying to be a resource that the rest of my team can learn from as far as what works. For example: when one of the people from our parent company asked about automating payroll entry, I threw their documents and discussion at Claude to see what it'd build. That plus churning on their feedback was ~30 hours of API usage right there.

I'm currently experimenting with "loops", and using codex in those loops to provide feedback and review. That gives me fable-like autonamy (that 30 hours of API usage above), maybe even better. But it uses a lot of tokens. Loops is the bulk of why I got to the weekly limit last week.

Plus I'm having it build an experiment on what my ideal "agent mux" would look like. Herdr is really close, I found it after I started that experiment. Now I'm just letting it run when I have spare usage to see what it comes up with.