● whenaireset

Grok reset — July 15, 2026

REGULAR Direct reset 2026-07-15 2026-07-15 @xAI

$ Grok reset usage limits for everyone on July 15, 2026.

xAI open-sources Grok Build under Apache 2.0 (xai-org/grok-build, almost entirely Rust, targeting Grok 4.5) and resets quotas on every account at the same time. Background: on 10 July a security researcher disclosed that early versions of the CLI uploaded entire Git repositories — commit history and secrets in .env included — to a Google Cloud Storage bucket, and the privacy switch did not stop it. If you ran the CLI in a repo containing secrets before 13 July, treat those credentials as leaked and rotate them.
Original text +

xAI 用 Apache 2.0 开源 Grok Build(xai-org/grok-build,几乎全是 Rust,面向 Grok 4.5),同时重置了所有账号的额度。 背景:7 月 10 日有安全研究者披露,早期版本的 CLI 会把整个 Git 仓库(含提交历史和 .env 里的密钥)上传到一个 Google Cloud Storage 存储桶,而且隐私开关拦不住。7 月 13 日之前在含密钥的仓库里跑过 CLI 的,应该把那些凭证当作已泄露来轮换。

source ↗ https://github.com/xai-org/grok-build

The provider wiped usage directly — nothing for you to do.

// CONTEXT

// NOTIFY ME

Email me when Grok resets

One email per official reset. No digest, no marketing, one-click unsubscribe. Prefer X? Reset alerts are also posted at @XIAOMIAO_26 · RSS

All Grok records →

Since June 2026 xAI folded every product into a single weekly compute pool, and stopped publishing any per-tier numbers.

// WHERE TO CHECK

Grok web / app
Settings → Usage has a percentage bar, a per-product breakdown and your next reset time
Reset voucher
When your account holds a redeemable reset, a "Reset available" badge appears next to Usage
Grok Build CLI
Usage lives in Settings → Usage; /feedback in the CLI is for reporting problems

// ERRORS