Skip to content

Tracking Antigravity usage: three views that answer different questions

CLI databases, IDE history files and the provider page each know something the others do not.

3 min read

Tracking Antigravity usage is mostly a question of knowing which artifact you are reading. The CLI writes conversation databases to disk, the IDE writes a different format, and the provider's own page knows about subscription capacity that neither of the other two can see. Keeping those three apart prevents most confusion.

The three views

View What it knows What it misses
CLI conversation database Tokens, models, sessions, timestamps Any quota or balance
IDE history files Editor-side history Not compatible with the CLI reader
Provider subscription page Plan capacity and resets Detailed per-session token history

A local tracker sits in the first row. It can tell you that a week was heavier than the last three, and it cannot tell you how much of the plan remains. UsageAtlas documents that boundary in its Antigravity CLI guide.

What counts as a good signal

If you are choosing a tracker, three properties matter more than the interface.

It reads what the tool already wrote. No API key, no proxy, no instrumented binary. UsageAtlas works this way for Antigravity CLI, reading supported .db files from the conversations directory.

It keeps history past the billing cycle. A dashboard that resets monthly answers "how much is left", not "was this month unusual".

It separates model and session. A single long run and a hundred small edits can cost the same and mean very different things.

Setting up the local read

The steps are short and the order matters.

  1. Run Antigravity CLI on the same machine, so there is history to read.
  2. Install the tracker and enable Antigravity CLI under its sources settings.
  3. Refresh and filter to the tool.

If the list stays empty, check the file path first. UsageAtlas reads a directory under the home folder, and the provider documentation names alternate locations plus an environment override. A file owned by another user is unreadable even if it exists.

Why the IDE files do not help

This is the detail people trip over. Installing the IDE does not create compatible CLI history, and its .pb files are a different format. A tracker that claims to read both is either converting something undocumented or overstating its coverage.

Ask what format a tool parses before believing a feature table.

Limits, stated plainly

A local reader cannot see subscription quota. It also cannot alert on a reset it does not know about, and its cost figures are estimates rather than charges.

That is not a flaw in the tracker; it is the boundary of the data on disk. Plan capacity against the provider, and plan habits against the local history.

When a local tracker is worth installing

If you run two or more coding assistants, yes, almost immediately. The value is comparative: seeing that one tool consumed four times the tokens of another for the same week of work is the kind of fact a per-vendor dashboard hides.

If you run one tool and check its own usage page weekly, you can skip it. The habit is doing most of the work.

FAQ

Does a tracker need to see my prompts?

No, and a good one does not want to. UsageAtlas reads usage metadata rather than prompts or responses.

Can I track Antigravity on a machine I do not administer?

Only if the account running the tracker can read the conversation files. Permissions decide that, not the tool.

Is the local history complete?

It covers sessions the CLI recorded on that machine. Work done elsewhere, or in the IDE, will not appear unless a compatible source exists.

FAQ

Does a tracker need to see my prompts?

No, and a good one does not want to. UsageAtlas reads usage metadata rather than prompts or responses.

Can I track Antigravity on a machine I do not administer?

Only if the account running the tracker can read the conversation files. Permissions decide that, not the tool.

Is the local history complete?

It covers sessions the CLI recorded on that machine. Work done elsewhere, or in the IDE, will not appear unless a compatible source exists.

Originally published on claudegpt.si