Antigravity — UsageNow Docs

UsageNow shows Antigravity’s weekly usage limits — one window per group of models — and your plan, while the Antigravity app is running.

Requirements#

The Antigravity app installed and running, and signed in

The Antigravity CLI (agy) on its own isn’t enough: its local server keeps its access token in memory, so UsageNow can’t read it. The app must be running.

How it works#

The Antigravity app runs a language server on a loopback port and prints that port and a CSRF token in its own command line. UsageNow reads just those two arguments (via ps), finds the socket with lsof, and asks the server for the same quota summary the app’s /usage panel shows.

Antigravity’s limits are shared by groups of models, so each group appears as its own window — for example 5-hour · Gemini and Weekly · Claude and GPT.

No credentials are involved

UsageNow never reads the Google sign-in Antigravity saved, never reads any other process’s arguments or memory, and sends nothing beyond 127.0.0.1. The loopback server uses a self-signed certificate, which UsageNow accepts for loopback addresses only. It never calls Google directly.

When the app isn’t running#

There’s nothing to ask, so the last limits UsageNow read stay for a day, marked stale, with Open the Antigravity app to update usage limits. Antigravity reports no token or model activity, because it stores conversations in an undocumented binary format and UsageNow doesn’t guess at numbers.

States#

What you see	What it means	What to do
No Antigravity section	Antigravity isn’t installed, or it’s turned off in Settings.	Install Antigravity, or turn it on in Settings › Providers.
Open the Antigravity app to update usage limits.	The Antigravity app isn’t running, so its limits can’t be read now.	Open the Antigravity app. Limits appear on the next refresh.
Antigravity usage limits are temporarily unavailable.	The app answered, but its reply couldn’t be used.	Wait and refresh later.