Conversation
gnayhz
added a commit
to gnayhz/grok2api
that referenced
this pull request
Aug 24, 2026
…, console quota reconcile, provider-prefix models, access-cookie auth, privacy diagnostics, doom-loop guards Functional picks from upstream: chenyme#995 SuperGrok Plus paid-tier recognition, chenyme#998 shared weekly limits for Web Imagine, chenyme#1002 statsig refresh on stale-page media rejection, chenyme#1003 console quota reconciliation after 429 (transient 5xx/429 no longer cascade into durable cooldowns), chenyme#1001 provider prefixes preserved in public model names, chenyme#1000 scoped access-cookie fallback for stripped bearer auth, chenyme#983 privacy-safe request diagnostics with bounded retention, chenyme#994 output doom-loop guards with split content/reasoning thresholds, serde hardening (output_text.annotations, model backfill, Anthropic marker filtering). Excluded: upstream quality-guard sidecar and its tooling/pages/config (superseded by the built-in quarantine/rotation guard), account-egress lease-block routing tests (superseded by scopeless pools). Kept our semantics where they diverge: strike-preserving clear-cooldown endpoint plus a new explicit /clear-cooldown-force, strict routing targets, RSC-clean confirmation gate, rotating fixed targets.
gnayhz
pushed a commit
to gnayhz/grok2api
that referenced
this pull request
Aug 27, 2026
fix: reconcile stale Grok Console quota after 429
gnayhz
added a commit
to gnayhz/grok2api
that referenced
this pull request
Aug 27, 2026
…, console quota reconcile, provider-prefix models, access-cookie auth, privacy diagnostics, doom-loop guards Functional picks from upstream: chenyme#995 SuperGrok Plus paid-tier recognition, chenyme#998 shared weekly limits for Web Imagine, chenyme#1002 statsig refresh on stale-page media rejection, chenyme#1003 console quota reconciliation after 429 (transient 5xx/429 no longer cascade into durable cooldowns), chenyme#1001 provider prefixes preserved in public model names, chenyme#1000 scoped access-cookie fallback for stripped bearer auth, chenyme#983 privacy-safe request diagnostics with bounded retention, chenyme#994 output doom-loop guards with split content/reasoning thresholds, serde hardening (output_text.annotations, model backfill, Anthropic marker filtering). Excluded: upstream quality-guard sidecar and its tooling/pages/config (superseded by the built-in quarantine/rotation guard), account-egress lease-block routing tests (superseded by scopeless pools). Kept our semantics where they diverge: strike-preserving clear-cooldown endpoint plus a new explicit /clear-cooldown-force, strict routing targets, RSC-clean confirmation gate, rotating fixed targets.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/usagesnapshot before treating an account as quota-exhausted.Retry-Aftercooldown when Console quota remains available.Why
A Console
resource_exhausted429 does not always mean the account has depleted its weekly quota. It may also represent a transient upstream rate limit.Previously, routing could continue using an old quota snapshot while repeatedly applying account failure penalties. This caused accounts with remaining quota to enter increasingly long cooldowns, and switching accounts could reproduce the same failure across the pool.
Behavior
failure_count, then allow normal account rotation.Tests
Added coverage for:
Verified with:
go test ./... -count=1go vet ./...go build ./...git diff --check