Cover Cursor and Antigravity, the sources that need a token

Almost every source tokenstat supports is a file. It gets read offline, with no credential and no network, which is why tokenstat scan can promise both.

Cursor usage needs its vendor API. Antigravity IDE collection needs the running app's local service. Their setup differs from ordinary on-disk sources.

Why these two are different

Cursor writes no token counts to disk. Every usage counter in its local state reads zero. That was checked rather than assumed. There is no file to parse, so the only way to cover Cursor at all is to ask its API for aggregate usage.

Antigravity's IDE sessions are not on disk until the app puts them there. Its CLI conversations are ordinary files and get scanned offline like anything else. The IDE half lives behind the app's local language server, so it needs the app running and a fetch to pull it across.

Connecting one

tokenstat auth cursor
tokenstat auth antigravity

With no --token, this looks for a credential the vendor's app already left on your device, the macOS keychain today. Nothing is invented and nothing is asked of the vendor beyond aggregate usage.

If you would rather hand it over yourself, paste one:

tokenstat auth cursor --token <token>

Then pull:

tokenstat fetch

fetch retrieves available remote usage and caches records for scanning. Run tokenstat scan afterwards to update the usage archive. Cursor fetches use a 30-minute cache; tokenstat fetch --force requests a refresh. Antigravity quota stays separate from token events.

Checking and undoing

tokenstat auth --status

Reports if tokens are available, per vendor. It prints no secrets, so it is safe in a terminal you are sharing or recording.

tokenstat auth cursor --logout

Forgets the stored token. The archive keeps the usage it already fetched, since that is your usage history rather than the credential.

What this does not change

The auth commands configure vendor usage fetching. Other connected features, including desktop plan-limit readings and agents, may also use available vendor credentials. See what tokenstat accesses.

Fetched usage is normalized into counters and metadata in the usage archive. Workspace conversation features handle content separately. What leaves your device when you sync covers the separate question of what an optional sync uploads.

Antigravity quota stays separate. How much of your plan remains is status, not usage. It is reported on its own and never turned into token events to make a chart look complete.

Related

• Which tools tokenstat reads, and what each one records is the full source table, including everything that needs no credential at all.
• Is tokenstat safe to run? covers the boundary these commands sit inside.