"You've Reached Your Free Grok Build Usage Limit": What Grok's Rate Limits Actually Mean
Grok's limit banner names no reset time, and since June 2026 paid plans run on one shared weekly usage pool instead of per-product caps. What the free-tier message means, how the pool works, and how Grok compares to Claude Code and Codex.
You're coding in Grok Build and it stops with: "You've reached your free Grok Build usage limit for now. Get SuperGrok for much higher limits…" No countdown, no reset time — just an upsell. If you've also used Claude Code or Codex, that's a jarring contrast: both of those tools at least tell you when you'll be unblocked. Grok's banner doesn't — on paid plans the weekly reset date sits in Settings → Usage instead — and that's not a bug in the wording: what's being metered is a shared, compute-weighted budget rather than a session clock.
Free and paid Grok are metered differently
The first source of confusion is that "Grok" isn't one product. Grok Build is xAI's coding agent CLI — the one you'd actually be running alongside Claude Code or Codex. grok.com (and the X app) is the consumer chat product. xAI says it began moving paid plans from separate daily product limits to one shared weekly usage pool across Chat, Imagine, Voice, and Build in June 2026. The rollout and allowance can depend on the account, so check the official Grok FAQ for the current description.
If the banner you see says You've reached your free Grok Build usage limit for now. Get SuperGrok for much higher limits…, treat it as the message shown for that account and surface, not as a universal published quota. xAI's current FAQ does not list a fixed free Grok Build count or reset time. It documents a weekly pool for paid plans and says free Chat and Voice allowances are separate. For a paid account, check Settings → Usage for its remaining pool and reset time.
Some older guides quote a limit of 20 Grok questions per two hours. I could not verify that as a current, universal limit in xAI's public FAQ. Don't apply that number to Grok Build or assume it applies to every account. xAI says free Chat and Voice have separate allowances but does not publish fixed counts there; check the in-product Usage view for the limit on your account.
Connect the Claude or Codex you already pay for — the rest runs on workers that cost a fraction.
Download meshcode →How the paid weekly pool works
These services do not share one reset model. Anthropic says Claude usage uses a rolling five-hour session window, with additional weekly limits on paid plans; Claude Code and chat share that allowance. OpenAI says Codex usage limits vary by plan and directs users to Settings, the usage dashboard, or /status for their current allowance and reset time. For paid Grok plans, xAI documents one weekly pool shared across its products. The Usage tab shows the remaining percentage, product breakdown, and reset date. xAI also says products consume different amounts of compute, so a long coding task can use more of the pool than a chat message. See Anthropic's plan details, OpenAI's Codex usage guide, and xAI's Grok FAQ.
When a paid plan reaches its weekly limit, xAI says paid features pause until reset, but the account can continue through Extra Usage Credits, Auto Top Up, or an upgrade. xAI's FAQ says credits start at $5, can currently be purchased on the web, expire one year after purchase, and use standard rates. Check xAI's current terms before buying because these options can change.
What actually helps once you've hit any of these
None of the three fixes below depend on which exact wording you saw:
Check the tool's own status, not a memory of a number. Codex has /status, Claude Code has /usage, Grok's is Settings → Usage on web and mobile. Thresholds change over time on all three, so a number you saw in a forum post six months ago is more likely to mislead than help.
Don't confuse the products. If you're getting rate-limited inside an editor extension (Cursor, Copilot, Kilo, Continue) while using a Grok model, that 429 is coming from the host, not from xAI directly — a different limit with a different fix (check the extension's own rate-limit settings, not Grok Build's).
Compare the cost of waiting with the cost of paying as you go. A prepaid balance can avoid a subscription reset window, but it is not automatically cheaper or unlimited. Track usage and set a spend cap before switching.
The meshcode angle
meshcode is a native desktop app for macOS and Windows built around running several agents in parallel panes. You can connect your existing Claude Code, Codex, or Grok subscription into its own pane through the CLI you already use — same billing, same limits, nothing extra from meshcode. Alongside it, meshcode's own metered model runs pay-as-you-go with no monthly fee and no shared window at all: no clock, no weekly pool, just a balance you top up when you choose to.
The point isn't replacing any of these tools — it's having somewhere to go the moment one of them says "come back later," instead of actually coming back later. If you want the same breakdown for the other two, we covered what Claude Code's usage limit message actually means and why a Codex quota tracker site is a symptom, not a fix. If you're deciding what to pay for Grok in the first place, see the cheapest way to use Grok for coding.
Sources and currentness
I checked the plan descriptions on 2026-10-07. xAI's FAQ documents its paid weekly pool and separate free Chat and Voice allowances; Anthropic and OpenAI describe their own plan-specific usage rules. Exact limits and reset times can vary by plan and account, so use the provider's Usage or Settings page for the value shown to you.
👉 Download meshcode — Mac, Windows.
More from the blog
Cursor Usage Limit Explained: What Happens When You Run Out of Included Usage
Cursor doesn't count discrete requests anymore — it meters two dollar-denominated usage pools that reset with your billing cycle. Here's how Cursor's Pro/Pro Plus/Ultra quotas actually work, what happens when you run out, and how that compares to Claude Code, Codex, and Grok's time-based limits.
"You've Hit Your Usage Limit": What Codex CLI's Usage Limit Message Actually Means
Codex CLI's 'You've hit your usage limit' banner isn't a hard daily wall — it's a rolling window with a short cap stacked under a weekly one, and the timestamp you see is computed from your own start time. Here's how to decode the message, why the weekly limit is the one that hurts, and what /status actually tells you.
How to Make Your Grok Subscription Last Longer: What We Actually Measured
What burns through Grok Build's usage limit isn't the prompts you type — it's the files the agent reads on its own. We measured exactly how much flows into one session, and changed how meshcode launches Grok to match what we found.