Gemini CLI quotas are the clearest example of a rule that depends on context: the same command can be metered four different ways. The UsageAtlas guide sorts them, and the ordering matters because the first check eliminates three of the four possibilities.

The sorted paths

Rank Path What it means for you
1 Personal Google account Free-tier limits that roll
2 API key Per-token billing with rate limits
3 Vertex AI project Project quotas and billing
4 Workspace Whatever the admin configured

Ranked by how often they are the answer, not by quality. Most individual developers are in the first row until an API key appears in their environment. The UsageAtlas guide sorts the same four.

The checks that settle it

Run the help command, then echo the two environment variables a key would use. That takes ten seconds and prevents most wrong diagnoses.

If a key is set, the question becomes the project's usage in the console. If none is, the free-tier rules apply and the CLI's own output is the place to read them.

Where the quota goes

Four behaviours, each fixable.

Repository-wide context. Ask for the file, not the folder.

Long sessions. Start a new one per task so context is not resent.

Verbose instructions. They are charged every turn.

Large models for exploration. Use the smallest that answers the question.

What changed in June 2026

Free and Google One users moved to Antigravity CLI. That means the limits, the reset behaviour and even the location of the quota panel may differ from what an older guide describes.

Antigravity CLI has its own guide and its own panel. Reading the current tool is faster than reconciling two sets of rules.

Why local tracking still helps

A quota tells you when to stop. A token record tells you what to change. The second is the one that reduces the frequency of the first.

UsageAtlas reads Antigravity CLI session files for supported tokens, models and sessions, free and open source, with no account for local tracking. It does not report subscription quota from that source, which is the correct boundary rather than a gap to work around.

A tracker that showed an invented remaining percentage would be worse than one that stayed quiet, because you would plan against it. The honest version shows what it read and says what it could not see.

The planning rule that survives

Whatever the meter, plan against what the tool reports and change behaviour based on what your sessions consumed. Two sources, two jobs, and no inference in between.

FAQ

Is there a single Gemini CLI quota number?

No. It depends on the login, and the CLI or console reports the one that applies.

Can a local tracker show my remaining quota?

Not for this tool. It can show what your sessions consumed.

Should I remove my API key to get the free tier?

Only if that is the account you intend to use. A key is a billing choice, not a bug.

The takeaway

Check the login first, read the panel second, reduce context third. The order saves the most time.