upvote
What are you guys doing to burn through limits?

I have some dev + prod bots and according to ccusage, use the equivalent of $2500/month with them on CC yet I never hit the rate limits.

I feel like I'm using them all the time so I'm curious what you are actually doing that's burning all of these tokens.

Can you give me an example?

For me, it's:

  1. Write a spec for <feature>
  2. Add design for issue
  3. Write code
  4. Deploy code and manage configuration
  5. Run analytics
reply
I don't get it either. Earlier this week I had Claude build a POC for a tool we're evaluating. I spent a few hours building out a requirements doc in a chat with Fable. Then Claude Code built it with Fable as the manager and the code being written by about 80% Opus/20% Sonnet subagents (this was using superpowers). It ran continuously for 15 hours on the implementation and didn't hit any limits.
reply
My uses cases are mainly research and prototyping, often starting from scratch in greenfield projects. The 5-hour quota is shared between Claude web and Claude Code, so it doesn't really matter what interface I use.

When it comes to research, my prompts are already narrowed down to specific topics, and I even include examples and break the process down into stages. For development tasks, I try to avoid a mono-repo in the beginning and develop modules before combining them together to avoid distracting the AI's attention and minimize the overhead.

With Codex, on GPT-5.6 Sol with xhigh effort, I need to go several rounds and at least 2-3 hours before hitting the (now-removed) 5-hour limit, which translates to 10% of the weekly usage. In contrast, I run out of quota even with Claude Sonnet.

In terms of quality of output, Codex digs deep for research tasks, in the right direction, produces less AI slop, and follows my direction better. At least that's how I perceive it. But again, the main problem with Claude is running out of quota in the middle of research or implementing a task.

reply