Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Gemini CLI error

Gemini CLI: Usage limit reached for <model>

Error message
Usage limit reached for <model>.

Status: Fixed in releaseLast verified 2 documented fixes3 sources

What it means

A terminal quota error for the current model: the daily quota for that model is used up. The dialog adds the reset time when known, plus "/stats model for usage details", "/model to switch models." and, for Sign in with Google, "/auth to switch to API key."

Causes

  • The daily quota for the model is exhausted (core also reports "You have exhausted your daily quota on this model.").
  • Maintainer (bdmorgan, #16704): a backend issue made usage limits inconsistent between the backend and the CLI, so /stats showed remaining quota while requests were blocked (often from unsynchronized token limits or incorrect model routing). AI Pro and Ultra subscribers also did not always get their higher tiers.

How to fix it

  1. Fix 1.

    Use the in-CLI options from the message: /stats model to view usage, /model to switch models, or /auth to switch to an API key.

    Slash command
    /stats model
  2. Fix 2.

    If /stats shows remaining quota while you are blocked, update to the latest version, as maintainers asked in #16704 (closed as fixed on 2026-01-28).

    Terminal
    npm install -g @google/gemini-cli

More Gemini CLI errors

All 19 Gemini CLI errors

FAQ

What does "Usage limit reached for <model>" mean in Gemini CLI?

A terminal quota error for the current model: the daily quota for that model is used up. The dialog adds the reset time when known, plus "/stats model for usage details", "/model to switch models." and, for Sign in with Google, "/auth to switch to API key."

How do I fix "Usage limit reached for <model>"?

There are 2 documented fixes. Start with the first: Use the in-CLI options from the message: /stats model to view usage, /model to switch models, or /auth to switch to an API key.

Is this Gemini CLI error fixed?

Status: Fixed in release. A release fixed this. The affected versions note says where the fix landed. Affected versions: False-positive variant reported on 0.24.0 (#16704)

Sources

Last verified against 3 sources: official docs, maintainer replies and release notes.

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.