Your weekly Grok Bot limit resets. Two days later it says 100%. You didn't sit in chat all week. So where did it go?
Short answer: mostly into work you never watched happen. Routines firing on a schedule, bots handing tasks to other bots, long chats getting re-read on every run. This post walks through what people on X reported over the last two weeks, why it happens, and the eight fixes that actually move the number.
What people are reporting
The pattern is the same everywhere: the drain comes from background work, and nobody can see it.
Hit my Grok Bot usage limit yesterday. Not even with Grok Code, just my setup (bots, routines, handoffs). I can't really see what's eating it.
I can't see how much of my weekly limit I've used or what's eating it, so I keep guessing which routines to cut.
@a1254766624 built a dashboard to find out:
last 7 days: 14% → bots talking to other bots
one bot alone = 8%
62.8% of my weekly limit gone by friday
Others hit the wall even faster. @500karch burned "95% of my weekly limit in 3 days." @testafortedev went from "21% of my weekly limit at 2 PM, 69% by the next morning." And a brand new user, @raminguliev86, said: "in 1 day I burned my entire weekly Premium usage plus $23 in extra credits just setting it up."
Why it feels worse lately
The unified X Subscription. Several people noticed the change right after switching. @BoilerPaulie: "Before, I could hit my limit on Grok Bot and Grok Build separately, but now I'm stuck at 100% usage on both with 3 days until reset." @diweixia: "Normally, I would rarely exceed 75% utilization after a full week," but after unifying, "almost burned through my weekly limit in 2 days."
One shared pool. @imohitmayank put it plainly: "now Imagine, Grok Bot and Cursor all pull from one weekly pool." One Imagine session "took 7% of my week." @Supercolor76442 asked whether the allowance is now shared "across Grok, Imagine and Grok Bot." The @grok account confirmed it: "Grok Bot usage draws from a shared weekly pool (with Grok and Cursor) on Premium/Super/Ultra plans."
Serving costs. Elon Musk said "The cost of serving Grok Bot was unsustainably high relative to revenue." @Layton_Gott's post on users "suddenly hitting theirs days early" picked up over 250 likes. Elon is also asking what to improve, so feedback is landing.
Extra credits are not a safety net. @OAKTEK: "even tried the on demand limit and wow 20$ vanished and almost nothing was done." @BoilerPaulie said it "burned through all $20 of my extra credits."
And when you hit the cap, things stop. @thelastminute: "If you hit your usage limit... reminders/routines seem to no longer trigger." Some users also report the dashboard disagreeing with itself. @Jimmy_FanFan saw "Weekly usage limit reached" next to "11% used."
You can't change the pool. You can change what you pour into it.
Where the usage actually goes
Think about what one routine run costs. The bot loads its instructions, re-reads the chat history it lives in, calls tools, maybe opens a browser, writes output, and maybe hands off to another bot, which does all of that again. Now multiply by how often it runs. A routine that is "small" but runs hourly is 168 runs a week. A long-lived chat gets more expensive every time it is re-read.
None of that shows up on your screen. That is why the limit feels like it vanishes.
8 fixes, in order of impact
1. Lower the frequency
@justinfredette has the best rule I've seen:
if nobody reads it, it shouldn't run daily.
His method: export your usage, mark the outputs you actually read, and slow down or retire the rest. Hourly becomes a few times a day. Daily becomes weekly.
2. Use flexible timing
If a routine doesn't need to fire at 9:00 sharp, don't make it. Let it run "sometime in the morning" or only when something changed. @grok's own tip is to "space routines to hourly or a few times daily" and do a "change-check first": a cheap check that exits early when there is nothing new.
3. Tight, single-job routine prompts with short output
One routine, one job. "Check X, and if Y changed, send me 3 bullets" beats a page of instructions that asks for a full report. Output costs too, so cap it. Also run recurring work on a fresh bot or chat, as @grok suggests, "to avoid expensive long-chat re-reads."
4. Batch small routines
Five little routines each pay the startup cost five times. One routine that does all five checks pays it once.
5. Use low-effort workers for simple tasks
Sorting, formatting, checking a page for changes, summarizing a short email: none of that needs your heaviest setting. Save the expensive effort for work that needs real reasoning.
6. Cut bot-to-bot handoffs
Every handoff means another bot loads its context and does work. In @a1254766624's numbers, bots talking to other bots was 14% of the week. If two bots ping each other to confirm things, merge them or make one of them write a file the other reads later.
7. Pause idle bots
That experiment you set up three weeks ago and never check? It is still running. Pause it. You can turn it back on in a second.
8. Check usage every week
Pick one day. Look at the percent used, what ran, and what you actually read. Five minutes a week beats finding out on Wednesday that you're locked out until Monday.
Let a bot do the audit: Usage Saver
Doing all of that by hand is tedious, so I built a free Grok Bot template for it: Usage Saver.
- It reports your usage so you can see where the week went.
- It finds the biggest drains: the routines, bots and handoffs eating the most.
- It proposes savings, like a lower frequency or pausing an idle bot, and waits for your yes before changing anything.
Nothing gets paused or edited behind your back. You approve each change.
Get it here: https://x.ai/bot/TsvAlS9EqLm8hjObMxEbp
The takeaway
Your weekly limit isn't only spent by you. It's spent by everything you set up to run while you're not looking. Make that work visible, cut what nobody reads, and the same plan lasts a lot longer.
What's eating your usage? Tell me on X: @bobbyhalljr_dev.
Top comments (0)