Gemini CLI error
Gemini CLI: API error: 429 - Resource exhausted
API error: 429 - Resource exhaustedStatus: WorkaroundLast verified 3 documented fixes4 sources
What it means
The request was rejected because a rate limit or quota was exceeded (HTTP 429 Too Many Requests / RESOURCE_EXHAUSTED).
Causes
- Per the official FAQ, you have exceeded your API request limit; the Gemini API has rate limits to prevent abuse and ensure fair usage.
- Per the quotas doc, requests are limited per user per minute and depend on service availability at times of high demand. Daily limits: 1,000 requests for Gemini Code Assist (Individual), 1,500 for Google AI Pro, 2,000 for Google AI Ultra, and 250 for an unpaid Gemini API key.
- Maintainers opened tracking issue #24937 to centralize 429 and capacity reports.
How to fix it
- Fix 1.
Check your usage in Google AI Studio or your Google Cloud project dashboard.
- Fix 2.
If you send many requests in a short period, batch your prompts or add delays between requests.
- Fix 3.
If you consistently need a higher limit, request a quota increase or move to a plan with higher limits (see the Quotas and pricing page).
More Gemini CLI errors
All 19 Gemini CLI errorsYou must be a named user on your organization's Gemini Code Assist Standard edition subscription to use this service. Please contact your administrator to request an entitlement to Gemini Code Assist Standard edition.Status: WorkaroundFailed to sign in. Message: Your current account is not eligible... because it is not currently available in your location.Status: By designFailed to sign in. Message: Request contains an invalid argumentStatus: WorkaroundUNABLE_TO_GET_ISSUER_CERT_LOCALLY or unable to get local issuer certificateStatus: WorkaroundThis account requires setting the GOOGLE_CLOUD_PROJECT or GOOGLE_CLOUD_PROJECT_ID env var. See https://geminicli.com/docs/get-started/authentication/#set-gcpStatus: By designInvalid Google Cloud Project ID: "<projectId>". The GOOGLE_CLOUD_PROJECT (or GOOGLE_CLOUD_PROJECT_ID) environment variable must be set to your string-based Project ID (e.g., "my-project-123"), not your numeric Project Number. Please update your environment variables.Status: By designFailed to login. Message: Precondition check failed.Status: Fixed in releaseYou are currently configured to use a Google Cloud Project but lack a Gemini Code Assist license. Please contact your administrator to request a license.Status: Workaround
Related reading
- Do Your Agent Hooks Fail Open? Claude Code vs Codex vs Cursor vs Gemini CLIA guard hook that crashes, times out or points at a missing script lets the tool call through by default in Claude Code. v2.1.295 adds onFailure: block. Here is what each coding agent does when your policy hook breaks, with real test runs.
- How to Keep API Keys Away From Your AI Coding Agent: Claude Code vs Codex vs Cursor vs Gemini CLIA deny rule on .env stops cat but not a Python one-liner. Here are the three layers that actually keep secrets out of a coding agent's context - file rules, environment scrubbing and credential masking - and what Claude Code, Codex, Cursor and Gemini CLI give you for each, with real test runs.
- Headless AI Coding Agents in CI: Claude Code, Codex CLI, Gemini CLI, and opencode ComparedHeadless AI coding agents in CI compared: Claude Code, Codex CLI, Gemini CLI, and opencode on invocation flags, sandboxing, auth, and output formats.
- Gemini CLI to Antigravity CLI Migration Guide: The June 18 DeadlineGemini CLI to Antigravity CLI migration guide: install, migrate config, update scripts and CI, and avoid the silent MCP failure that breaks tool calls.
- Gemini CLI Guide: 1M Token Context and Who Can Still Use ItGemini CLI puts a 1 million token context in your terminal but now only serves paid Gemini API, Vertex AI and Code Assist users. Setup and TypeScript workflow.
FAQ
What does "API error: 429 - Resource exhausted" mean in Gemini CLI?
The request was rejected because a rate limit or quota was exceeded (HTTP 429 Too Many Requests / RESOURCE_EXHAUSTED).
How do I fix "API error: 429 - Resource exhausted"?
There are 3 documented fixes. Start with the first: Check your usage in Google AI Studio or your Google Cloud project dashboard.
Is this Gemini CLI error fixed?
Status: Workaround. No release removes the cause. The documented fixes work around it. Affected versions: All versions; ongoing reports tracked in #24937
Sources
Last verified against 4 sources: official docs, maintainer replies and release notes.
- github.comhttps://github.com/google-gemini/gemini-cli/blob/main/docs/resources/faq.md
- github.comhttps://github.com/google-gemini/gemini-cli/blob/main/docs/resources/quota-and-pricing.md
- github.comhttps://github.com/google-gemini/gemini-cli/issues/24937
- github.comhttps://github.com/google-gemini/gemini-cli/issues/1502
Newsletter
Fixes for the tools you use, weekly
One email per week. New coding agent releases, what broke, and how developers are working around it.