← All fixes
429Google· Rate limits

Gemini CLI “Quota exceeded” (429) — how to fix

429: Quota exceeded for quota metric …
Quick answer

Gemini CLI's free tier has per-minute and per-day request quotas. Agentic sessions (many tool calls) hit the per-minute cap in bursts and the daily cap on long days; both reset automatically. Paid API keys raise the quotas.

What causes it

How to fix it

  1. Wait — per-minute limits clear in seconds, daily limits at midnight Pacific.
  2. Attach a paid Gemini API key (or Code Assist license) for higher quotas.
  3. Reduce agentic parallelism and unnecessary tool calls.
  4. Run volume work on an unmetered agent so the free quota is reserved for Gemini-specific strengths (1M context).
Running an agent?

A single “fix this repo” prompt can trigger dozens of requests. Free-tier daily quotas are sized for chat, not agent loops.

The permanent fix

Stop hitting this entirely

Gemini CLI is Google-model-only, so you can't repoint it. But OpenCode, Aider, and Cline do the same terminal-agent work on Standard Compute's flat-rate endpoint with no per-minute or daily quotas — a common setup is Gemini CLI for giant-context tasks, an unmetered agent for everything else.

Get a free API key →How it connects →

FAQ

When does the Gemini CLI daily quota reset?

Daily quotas reset at midnight Pacific time; per-minute quotas roll continuously.

Related errors

429 Too Many Requests — what it means & how to fixAny provider · 429Codex “You've hit your usage limit” — how to fixOpenAIWhy your AI agent keeps getting rate limited (and how to stop it)Any agent