Grok Bot usage limits still cut off real sessions, user says
A user acknowledges Grok Bot's usage improvements but says limits still interrupt real sessions, and suggests pre-run cost estimates, a bigger pool, less tool-loop waste and separate quotas.
Grok Bot got a lot better on usage. But I keep hitting the limit in a real session. Options I can think of... 1. A cost check before a big run. Tell me this task will use about 15% before it starts, not after it dies. 2. Make the computing usage pool bigger, more room. Most of us are not abusing it. We are mid-build when it cuts off. 3. Make the bot waste less. Shorter tool loops, cache the file it already read, stop re-planning a task it already solved. Efficiency could beat a bigger pool. 4. Split the pool. Small questions should not eat the same bucket as a long build.