Time waiting
4 days
Last reset
Time waiting
11 days
Last reset
Time waiting
10 days
Last reset
Last reset
09-05
18:24
Resets in 30 days
2
Next, estimated
09-17
About 19 hours to go
MarAprMayJunJulAugSep
Colors mark events for all or paid users. Select any date to see all records.
Reset records
3 eventsSwipe sideways for the full table →
| Date | Type | Applies to | Reason | Post |
|---|---|---|---|---|
| 09-0518:24 | Usage reset | Some usersGrok Bot users | Unstated | |
| 08-2617:23 | Usage reset | Some usersGrok Bot users (weekly limits) | New productThe post also announces Bot access for SuperGrok and Cursor Pro subscribers | |
| 08-1317:49 | Usage reset | All users | New modelGrok 4.6 launch | Post |
| ||||
We record extra usage resets announced for Grok and Grok Bot. Grok Bot has its own allowance: a Bot reset does not refill Chat, Imagine or Build. Check Settings → Usage in Grok for your regular weekly reset time.
FAQ
Did Grok reset today?
Check the verified records and their scope above. Unreviewed announcements do not count toward reset statistics. No record means we have not recorded one; it does not prove no reset happened.
When does my weekly Grok allowance reset?
Check Settings → Usage in Grok for your account’s reset time. This site records extra official resets and reset tokens, not each account’s normal weekly refill.
Does a Grok Bot reset also refill Chat?
Grok Bot has its own allowance. A Bot-only announcement does not establish a refill for Chat, Imagine or Build. Check the scope of each record.
What was the August 13 reset?
This was a usage reset announced during the Grok 4.6 launch, recorded for all users. The post also includes instructions for using a reset token in settings. Check your account page for the required steps and current allowance.
Was the August 26 reset limited to SuperGrok and Cursor Pro?
The post makes two announcements: those subscribers gain access to Grok Bot, and weekly usage limits reset for all users. We retain the plan context and record all Grok Bot users as the reset audience, rather than turning access eligibility into a two-plan restriction.
Where do these records come from?
Third-party history pages supply leads. We verify the author, timestamp and wording of originals from @grok, @bot or @elonmusk. Posts about the same event are merged and counted once.