gemini-cli fix: monthly spending cap 429s now treated as terminal quota errors, ending retry loops
kabishou11 · ghdev · 2026-09-29
A P2 PR for gemini-cli fixes a quota-handling bug: when a 429 had empty details and the message indicated a project-level monthly spending cap, classifyGoogleError fell through to RetryableQuotaError, so the TUI kept retrying a non-transient error, resetting the attempt counter and looping the notice. The classifier now returns TerminalQuotaError for spending-cap messages on HTTP 400/429/499 before the fallback, and the quota dialog preserves the original API message instead of "high demand". Ordinary rate limits, 503s, and capacity exhaustion are unchanged; validated with 49 + 36 passing tests.
More from coding & agent
- Generic API-catalog MCP server vs one tool per job: a context-bloat experiment — MandeepKaur9407 · 2026-11-16
- Berkeley paper: LLMs answer with stale values even when the update is in context — ombre-ai · 2026-11-16
- Effective HTML: 4.2k-star agent skills turn wireframes into self-contained interactive prototypes — tom_doerr · 2026-11-16
- skills-gate: one gate skill fronts 148 agent skills at just 389 tokens — Distinct-Pie2389 · 2026-11-16
- Open-weight Karpo-Decision-31B tops Decision Index at 73.9, one forward pass per answer — CodeByPoonam · 2026-11-16
- shadcn boosts @uisdk: one-shot UI rebuild that's instantly E2E-testable by AI — shadcn · 2026-11-16