Agent HUD · Guides · Supported clients
Antigravity quota on Mac
Antigravity reports its quota through the language server running on your own machine, so the numbers appear only while it is up.
At a glance
| Quota | Buckets from the local server |
|---|---|
| Account | Email · team |
| Running · completion | No · Stop hook |
| Credentials read | None |
What you see
One row per bucket the server reports, with the period inferred from the bucket's own name — weekly or five-hour. The plan comes from your user tier.
How the account is named
The email and team the server reports. The IDE and the command-line tool can be signed in separately, so the two may not agree.
Running turns and completions
Running turns are not detected. Completions arrive through the Stop hook.
What Agent HUD reads
The conversation databases. No credentials are read at all: the running server's token is taken from its own command line and no login is attempted. Databases of the same name in different roots are treated as one conversation.
Common questions
- Why does Antigravity quota disappear when I quit it?
- The quota comes from the language server running on your Mac. With nothing running there is nothing to ask, so the last reading stays visible with its observation time and no new one arrives.
- Why are some of my sessions missing?
- A usage row counts only when it has a recorded timestamp or a unique link to a recorded step. File times are never treated as usage times, so rows that cannot be placed in time are excluded and a notice says so.
Last updated: 2026-09-20 · The behaviour described here is documented in full, with the code it comes from, in Agent HUD Open. providers.md