Skip to content
vibecodershq.
Submit a tool
SPONSOR SLOT · OPENPut your tool in front of builders choosing one right now. One slot, every page, $50 a week.Your tool here, $50 a weekClaim it

Grok Bot 8 min readUpdated 19 Oct 2026

Grok Bot Usage Limits: How the Weekly Pool Works and How to Stretch It

How Grok Bot usage limits work: the weekly shared pool, when it resets, what happens after it runs out, and practical ways to cut wasted usage.

Grok Bot usage limits work as a weekly pool. On The X Subscription, each paid seat gets a weekly pool of included usage that Grok Bot shares with Grok and Cursor. Your usage view shows how much you've used and the date of your next reset (xAI docs, Usage limits, checked Oct 19, 2026). Grok Bot is included on Premium, Super and Ultra, not on Plus. xAI publishes each tier's included usage as a multiple of Plus, not as a fixed number of messages or tokens. Once the pool is used up, further usage is paid Additional Usage from prepaid credit, and you can cap it. The second half of this guide covers how to make the pool last, mostly by cutting waste: group chats that wake every Bot, routines that keep re-checking the same sources, and chats that sprawl.

What the limits are

From xAI's Plans and usage page (checked Oct 19, 2026):

PlanMonthly list priceIncluded usageGrok Bot
Plus$8/moBaseNot included
Premium$30/mo4xIncluded
Super$100/mo15xIncluded
Ultra$200/mo50xIncluded

The multiples are relative to Plus. xAI doesn't publish the base amount as a number, so there's no official way to convert "4x" into a count of messages, tasks or routine runs. xAI's Usage limits page also says usage rates vary by product, so different activities draw different amounts from the pool. Team seats are listed at the same per-seat prices, and each seat includes the same usage as the matching individual tier. On self-serve team plans, seats don't share weekly pools.

If you haven't switched to The X Subscription, your existing Cursor or SuperGrok plan continues. xAI's Grok Bot on The X Subscription page says you check usage on cursor.com/dashboard before switching, and under Usage on grok.com/dashboard after.

When usage resets

The pool is weekly, and xAI says your live usage view shows the next reset date. We couldn't find a fixed reset day or time stated anywhere in xAI's docs, so check your own usage view rather than relying on a day of the week.

Rate limits, Additional Usage and spending caps

We found no published rate limit for Grok Bot itself. The limits xAI does document are structural. A Bot can own up to 50 routines, routine schedules must be at least five minutes apart, and the app keeps the 20 most recent run records per routine (Skills and routines, checked Oct 19, 2026).

When the weekly pool runs out, first-party usage becomes Additional Usage, paid from prepaid top-up credit. xAI's Spending caps page describes four separate controls: the weekly pool, the prepaid balance, a monthly additional usage limit and Auto Top-up, which is off unless you turn it on. Additional Usage stops when your balance is empty or the monthly cap is reached, and adding money doesn't raise the cap. Spend alerts warn you but don't stop usage; only the monthly limit does. You manage these under Additional usage credits on grok.com/dashboard.

On Team Bots, xAI's Team Bots page says a teammate's chats count against that teammate's allowance, and a routine counts against whoever set it up.

How to stretch your limit: cut the waste

A bigger plan doesn't fix waste. Greshamtrade reported seeing people burn a week of Grok Bot usage in a day, and argued that bloated chats, repeated tool calls and routines checking the same sources all day are the cause, not plan size. Here's what xAI's docs and our own practice suggest instead.

Stop group chats from waking every Bot

Karadokuy reported running out of quota in about two days with all their Bots in one group chat, where every message woke every Bot. They switched to messaging a single "director" Bot directly.

xAI's Message and collaborate page doesn't say how much a group message costs. It does say that writing normally in a group lets the participating Bots decide who should respond, and it suggests more targeted options:

  • Type @ and pick one Bot when one teammate owns the request.
  • Use Reply on a Bot's message to send your answer to that Bot.
  • Mention several Bots only when the request genuinely needs each of them.
  • Use @everyone sparingly.

xAI also says to ask for a single owner at each stage, because too many parallel handoffs can create duplicate work and noisy updates. In our view, keep groups for work that really needs a shared outcome, and send everyday requests to one Bot directly.

Narrow routines that keep re-checking the same sources

xAI's routines page warns against broad listeners such as "every new message", saying they create noise, consume usage and increase the chance of acting on irrelevant input. It recommends a narrow matching rule and a clear response. Some practical habits:

  • Schedule only as often as the source changes. In our view, a daily check on a source that updates weekly is mostly wasted runs.
  • Tell the routine what "nothing new" looks like. Our own Bot-design rule is to stay quiet when there's nothing to say. A routine that reports "no change" in one line costs less than one that writes a full summary every time.
  • Review run history. Under View conversation details → Routines, you can see recent runs, pause a routine, edit its schedule or delete it.
  • Watch for paused routines. xAI says Grok Bot may ask whether to keep routines running after a long period away, and pause them if you don't respond.

Keep chats lean

xAI's Bots page says a Bot can retain stable preferences, important facts and summaries of its work, so it can keep a role over time "without replaying every prior message". It also says memory isn't a substitute for an authoritative source. In our view, that points to some lean habits:

  • Save a repeatable method as a skill instead of re-explaining it in chat.
  • Keep changing facts in the source system and point the Bot there.
  • Ask for short outputs, like a linked page or a one-line status, rather than long recaps.

xAI's docs don't say how much a long conversation draws from the pool compared with a short one, so we haven't put a number on it.

Give each Bot one job

xAI's Bots page says a clear job, such as Expense Manager or Bug Reproduction, gives a Bot better guidance than a catch-all "General Helper". Our Grok Bot team guide sets out our own rules: one job per Bot, a written won't-do list, and staying quiet when there's nothing new. Bots like Meeting Prep, which sends a five-line brief before each meeting, show what a narrow, short-output job looks like.

How to tell which Bots earn their keep

We found no per-Bot usage breakdown in xAI's docs. The usage views show your pool as a whole. In our practice, we use a few proxies:

  • Run history: a routine whose last 20 runs all said "nothing new" is a candidate to slow down or pause.
  • Output you used: if you haven't acted on a Bot's reports in a week or two, narrow its job or pause its routines.
  • Overlap: two Bots checking the same source is a sign to merge the job into one owner.

Back up your setup

xAI's docs describe one way to save a Bot's configuration: Share menu → Create template. The Bots page says a template link shows the Bot's shared configuration, "including its identity, description, skills, and routines". Adding it creates a copy that doesn't include your computer, logins or conversation history. The Team Bots page says a copy's memory starts from what the template shares. Strip API keys, internal URLs and customer data first, and set the link to Team-only if you're on a team. xAI doesn't describe templates as a backup tool, and it doesn't say whether files on your computer or connector setups are included. In our view, keep important files somewhere else too.

FAQ

Does Grok Bot have its own usage limit? On The X Subscription, no. Grok Bot draws from the same weekly pool as Grok and Cursor for that seat.

When does Grok Bot usage reset? Weekly. Your usage view shows the next reset date. xAI doesn't publish a fixed reset day.

How many messages do I get? xAI doesn't publish a number. It lists included usage as multiples of Plus (4x, 15x, 50x) and says rates vary by product.

What happens when I run out? Usage becomes paid Additional Usage from prepaid credit. It stops when the balance is empty or your monthly additional usage limit is reached.

Do group chats use more usage? xAI's docs don't say directly. They recommend directing messages with @ or Reply, and using @everyone sparingly.

Sources

All checked Oct 19, 2026.