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
- AI.CLASSIFY coming to Quail: rethink OLAP-style AI operations on data — sh_reya · 2026-09-30
- Ant Group's Marathoner Trains Agents to Work 10+ Hours With 1000+ Tool Calls — antgroup · 2026-09-30
- Supply Chain Agent Lesson: Memory Knows the Rules, Code Enforces Them — Chemical_Pickle5979 · 2026-09-30
- Artificial Analysis open-sources agent inference benchmark, first results for DGX Spark, RTX 5090, M5 Pro — ArtificialAnlys · 2026-09-30
- Feed Your Agents Markdown: How a Good API Turned cf CLI Into an Unexpected Agent Tool — irvinebroque · 2026-09-30
- 14% of AI-Written Tests Were Useless: The Checker Rewarded Typing Words, So Agents Typed Them — Input-X · 2026-09-30