On this page

Separate identity from model

The model name does not tell you which plan is being charged. An agent may use a Gemini-family model while the allowance belongs to an Antigravity account or licensed workspace. Start by identifying the signed-in account, the provider surface, and the reset window.

This prevents a common confusion: seeing healthy Gemini API capacity and expecting it to explain an Antigravity limit, or the reverse.

Track quota and activity together

A quota meter answers how much capacity remains. Agent activity answers whether a process is still working, finished, or waiting for input. Both matter when autonomous sessions run in the background.

Super Notchy checks Antigravity's local service and available Google quota information where the account exposes it. When a direct quota is not available, a request count is still useful as a local pace signal, but it should not be presented as an official remaining percentage.

Keep your usage visible while you work. Get Super Notchy for $39 ↗

Keep a fallback plan

If Antigravity approaches its active limit, route a bounded task to Gemini CLI, Codex, Claude Code, or a local model only after checking that tool's own allowance. Multiple assistants help only when their counters are visible separately.

Record the reset time and the task that caused the largest jump. Over several days, that gives you a practical routing playbook for your own work.

Sources and further reading