"You've Reached Your Free Grok Build Usage Limit": What Grok's Rate Limits Actually Mean

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. Until June 2026 each product had its own daily limits; xAI's FAQ says paid plans now draw on one shared weekly usage pool spent across Chat, Imagine, Voice, and Build instead.

The Grok Build CLI's confirmed free-tier message is short and upsell-first: You've reached your free Grok Build usage limit for now. Get SuperGrok for much higher limits… — no reset time in the banner. xAI's own changelog says rate-limit errors now surface "specific server messages (capacity, team limits, free-usage)" depending on your plan and auth type, but the exact paid-tier wording isn't publicly documented — so if you're on SuperGrok and see something different, that's expected, not a bug.

grok.com's chat message is the one many people search for: You've reached your limit of 20 Grok questions per 2 hours for now. Please sign up for Premium or Premium+ to access more or check back later. That's the per-window question cap guides still quote. xAI's FAQ describes a move, rolling out from June 2026, from per-product limits to one weekly pool for paid plans, while free Chat and Voice keep their own allowances — separate from the paid pool, resetting on their own schedule. The FAQ lists no numbers, so we can't confirm today's exact free-tier wording.

How the paid weekly pool works

Claude Code and Codex both meter compute over a rolling time window — send your first message, a clock starts, and the limit clears a fixed number of hours (or a week) later, regardless of how many separate questions that involved. Grok's paid plans now meter compute too, but over a week: xAI describes one shared weekly usage pool you can spend across any Grok product, shown as a percentage used — with a per-product breakdown (API, Build, Chat, Imagine, Voice) and the reset date and time — in Settings → Usage. Products cost different amounts: a chat message uses little compute, while "running a long coding task uses far more," so a long Grok Build session drains the same pool a video generation would. That's why the banner has no fixed count to quote — what runs out is a budget, not a number of questions.

When a paid plan hits 100%, paid features pause until the reset, but xAI says it's "not a hard stop": you can buy Extra Usage Credits (from $5, web only, expiring a year after purchase, billed at standard rates — pricier per action than the usage included in your plan), turn on Auto Top Up, or upgrade. xAI's own advice is that if you regularly run out, upgrading beats repeated top-ups.

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).

Stop depending on any single shared limit at all. Whether it's a 5-hour rolling window or a weekly cap, all three are shared budgets you don't control the reset clock on. A prepaid, pay-as-you-go balance sidesteps the entire category — there's no window to refresh, no weekly pool to track, no "come back later."

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.

Stop waiting on someone else's reset clock: meshcode is free to start — download it and keep a metered pane ready for the moment any of your agents taps out.

👉 Download meshcode — Mac, Windows.