Grok Bot limit reached? How to keep your Bots working

  1. 1
    Open ReasonOn the web, or in the Reason app for Mac.
  2. 2
    Connect GitHubChoose the repository your Bots work in.
  3. 3
    Describe the taskReason does the work and opens a pull request.

Reason sessions run on Reason's cloud and use Reason credits.

Limit reached. Work keeps moving.

When Grok Bot says you've reached your usage limit, it isn't broken: your weekly pool is used up, and it comes back on the reset date in your usage view. To keep going now, add prepaid credit with a top-up or move to a bigger plan; to stop heavy coding work from using up the pool next time, have Grok Bot hand it to Reason or your own Claude Code or Codex while it still has usage, or start that work there directly.

Get your Bots working again in five steps

  1. Check the usage view and the reset date

    Open Usage at grok.com/dashboard, or Settings → Usage & Billing in Grok Bot. If the reset date is close, waiting costs nothing. If the meter jumped with no matching work, read what happened on November 1 and contact support@x.ai before you pay for more.

  2. Add a top-up for Additional Usage

    Under Additional usage credits on the billing page, choose Buy credits for a one-time top-up, or Set auto top-up to refill when the balance runs low. Usage past your weekly pool is paid from this credit. Check the Monthly additional usage limit too: when it is reached, paid usage pauses even with credit left. On a legacy Cursor plan, turn on on-demand usage instead.

  3. Move up a plan

    Premium includes 4x Plus's usage, Super 15x and Ultra 50x. If you hit the limit most weeks, compare the price of a bigger pool with what you spend on top-ups. Check current included usage at x.ai/pricing before you switch.

  4. Hand heavy coding work to Reason

    Open Reason on the web at reasonmachines.com, or in the Reason app for Mac, sign in and connect GitHub. Choose the repository and describe the task, for example "fix the failing tests". The session works in your repository on Reason's own cloud computer, runs the tests and opens a pull request, and it uses your Reason plan's credits, not your Grok weekly pool, so it keeps going whether or not Grok Bot has usage left. With Reason connected to Grok Bot, Grok Bot can also start a session for you; its own messages, including that one, still count toward the weekly pool.

Your options compared

OptionWhat you pay withBest when
Wait for the resetNothingYour reset date is a day or two away
Top-up (Additional Usage)Prepaid credit, used as you goYou need a few more tasks this week
Bigger planA higher monthly priceYou hit the limit most weeks
Reason sessionYour Reason plan's creditsCoding work: start it from Grok Bot while it has usage, or in the Reason app once it's out
Your own Claude Code or CodexThat agent's own plan; Reason Network is freeYou already run a coding agent; ask it directly once Grok Bot is out

What still counts toward your Grok pool

Everything Grok Bot itself does counts: its replies, its routines and the message where it hands a task off. What moves is the work behind the hand-off. A Reason session reads the code, runs builds and tests and opens the pull request on Reason's cloud machine; a Claude Code or Codex session does it on your computer. Grok Bot only relays the request and the answer.

Sources

Questions

How do I get more Grok Bot usage?

Add prepaid credit with a top-up for Additional Usage, or move to a bigger plan: Premium includes 4x Plus's usage, Super 15x and Ultra 50x. On a legacy Cursor plan, turn on on-demand usage. To use less of the pool, move coding work to a Reason session or your own coding agent before you run out.

How long does Grok Bot limit reached last?

Until your weekly pool resets on the date in your usage view, unless you add prepaid credit or upgrade first. With no credit and no on-demand usage, Grok Bot stops when weekly usage runs out and resumes when it resets.

Will a spending cap stop a Bot in the middle of a task?

Not always. xAI's docs say the cap does not stop a Bot in the middle of a run, so a running task can go a little past it. When the cap is reached, new paid usage pauses until the next month or until you raise it.

Is Grok Bot broken when it stops replying?

Usually not. If the Bot says you hit your usage limit, xAI's troubleshooting guide says your weekly usage is used up and it resets each week. If the meter doesn't match your work, contact support@x.ai.

Does handing work to Reason stop Grok Bot from using my weekly pool?

No. Grok Bot's own messages, including the one where it starts a Reason session, still draw from your Grok weekly pool. The coding work itself (reading the code, running builds and tests, opening the pull request) runs in the Reason session on Reason's cloud machine and uses your Reason plan's credits instead.

Is there a Reason plugin for Grok Bot?

Yes, and it is waiting on its Grok Bot marketplace listing. Until it is listed, tell Grok Bot to add the Reason MCP server https://mcp.reasonmachines.com/mcp: it is the same server the plugin connects to, and it lets Grok Bot start Reason sessions.

What does Reason cost?

Reason sessions use your Reason plan's credits, the same as working from the Reason app. Reason Network, which connects Grok Bot to your own Claude Code or Codex, is free.

More guides