Metrics
The Antigravity adapter declares UsageShape::NONE: it reads no token fields
from the harness’s output. Every normalized
token class is therefore zero, and because no
usage is reported, no cost is derived for a run.
Token classes
Section titled “Token classes”| Normalized class | Antigravity source |
|---|---|
| Uncached input | (not reported → null) |
| Cached input | (not reported → null) |
| Output | (not reported → null) |
| Reasoning | (not reported → null) |
UsageShape::NONE declares no JSON keys for any class, so the usage parser has
nothing to read and every class is null (not determinable) rather than 0. In
practice this is moot — Antigravity has no API-key mode, so it never produces a
run to record usage for.
Antigravity reports no self-reported cost field, and with no token usage there is nothing to price through OpenRouter either, so no cost figure is produced. This reflects the same limitation that makes the harness unavailable: Antigravity reports no token usage in its non-interactive mode (and authenticates only through a Google account), so The Test Cabinet has neither usage to normalize nor a runnable session to record. See the overview for that availability limitation.
See Metrics for the cost and token-class contract.