Figure: Example Antigravity Usage Intelligence dashboard in VS Code, showing token usage charts and quotas.
For developers building with Google Antigravity (an AI coding IDE), tracking how many tokens, API calls, and reasoning steps each workflow uses is crucial. The open-source Antigravity Usage Intelligence VS Code extension exposes hidden usage details: per-session token breakdown (input vs cache vs output vs internal reasoning), live quota status, and a GitHub-style activity heatmap. This article explains how Antigravity usage is measured today, how you can monitor it, and how the extension makes it visible.
How Antigravity Usage Works
Google’s Antigravity is an agentic development platform (using Gemini/Claude models) that runs multi-turn AI tasks. Unlike a simple chat, an Antigravity session can generate millions of tokens per task. In fact, in active projects “pairing with frontier models pushes tens of millions of tokens daily”. Antigravity uses cached context, internal “thinking” tokens (especially with Claude/Gemini), and external tools, so one session’s workload can vary greatly.
Antigravity’s subscription plans impose token quotas: Pro and Ultra users get the highest quotas refreshed every 5 hours (with generous weekly limits), while non-Pro accounts receive a smaller quota refreshed weekly. However, the built-in UI mainly shows whether a request succeeded, not a breakdown of usage. Developers face issues like:
- Hidden Context Burn: No visibility into whether an agent re-used 200K cached tokens vs rebuilding a fresh 200K token prompt.
- Buried Reasoning Overhead: Modern models consume extra internal reasoning tokens (e.g. Claude’s “thinking”), which aren’t shown.
- Unverified Quotas: Fixed limit alerts (e.g. “5-hour limit”) can be misleading if you want real-time remaining quota.
- Zero Session Forensics: No quick way to audit individual sessions (duration, tokens, tools used).
Antigravity Usage Intelligence solves this by running 100% locally and reading Antigravity’s session data. It connects to the local language server to fetch your account’s actual quota and then provides a real-time “command center” inside your IDE with the missing usage details.
Token Types and Data Sources
The extension breaks down tokens into categories. The table below describes each:
| Token Type | What it Includes | Example Source |
|---|---|---|
| Fresh Input | Non-cached prompt text (new input) | Your initial prompt or file contents |
| Cache Hits | Tokens served from Antigravity’s cache | Re-used conversation history or context |
| Output | Model-generated response tokens | AI’s answer text or code diff |
| Reasoning | Internal “thinking” tokens (Claude/Gemini) | Hidden multi-step reasoning tokens |
Example (7-day run):
- Total tokens: 2,800,000,000
- Cached tokens: 2,530,000,000 (∼90% from context cache)
- Output tokens: 220,000,000
- Reasoning tokens: 8,490,000
- Tool calls: 19,576
In this example, the vast majority of tokens came from the prompt cache (2.53B), highlighting how much work Antigravity saved by reusing context. These details only appear when you analyze the raw session data.
Live Quota Monitoring
The extension also keeps track of your subscription quota. It uses Antigravity’s local language server RPC to query your plan details and usage. The dashboard shows, for each model family (e.g. Gemini Flash, Claude Sonnet): your tier (e.g. Google AI Pro), remaining quota percentage, used prompt/flow credits, and a live countdown to the next refresh. For example, you might see:
Gemini 3.8 Flash — Used: 73% (Reset in 02:15:42)
Claude Sonnet 4.6 — Used: 88% (Reset in 02:15:42)
By default, Pro/Ultra plans reset every 5 hours. If the language server is offline, the extension falls back to a rolling 5-hour window estimate. You can configure warning thresholds (e.g. 75%, 90%, 100%) to get alerted before you hit a hard limit.
Daily Activity Heatmap
Figure: Example weekly activity heatmap (each cell = one day; darker green means more tokens used).
The extension includes a GitHub-style heatmap showing your activity over days and weeks. Darker tiles mean higher token throughput. There is also a 24-hour chart that highlights your peak coding hours. For example, you might discover that most of your token usage happens on weekday mornings, with evenings much lighter. These visual cues help you spot patterns (heavy coding days, all-nighters, etc.) at a glance.
Session Inspector and Tool Tracking
For detailed auditing, the Session Inspector pane lists individual sessions. For each session it shows: the unique session ID, project path, duration, turn count, and a token distribution bar (fresh vs cache vs output vs reasoning). It also lists what tools were used (e.g. run_command, view_file, grep_search, etc.) with counts. You can copy the session ID or export a markdown report. This makes it easy to investigate unusual cases: e.g. you might find one session used a large number of tokens because it ran a long grep_search on a huge codebase.
Installation
-
Via VS Code Marketplace: Open Extensions (
Ctrl+Shift+X), search for Antigravity Usage Intelligence, and click Install. Or install via CLI:
code --install-extension nirbhay-hiwse.antigravity-usage-intelligence
- Open VSX (e.g. VSCodium/Cursor): Run
ovsx get nirbhay-hiwse.antigravity-usage-intelligence
-
Manual VSIX: Download the
.vsixfrom the GitHub Releases and run:
code --install-extension antigravity-usage-intelligence-1.0.7.vsix
The extension relies on Python (no extra libraries). It auto-detects your Python installation. If needed, set antigravity-stats.pythonPath in settings to your python executable. After installation, it watches Antigravity’s local data and will automatically parse new sessions.
To use it, open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P) and run Antigravity Stats: Open Full Screen Dashboard. This opens the interactive analytics view. You can also enable a daily token count in the status bar via the antigravity-stats.showStatusBar setting, and refresh data manually with Antigravity Stats: Refresh Stats.
Security: The extension uses read-only access (?mode=ro) to Antigravity’s local SQLite databases and connects only to 127.0.0.1 (no internet). No external telemetry is sent.
Localization & Geofactors
All timestamps and charts use your system’s local timezone. For example, if your computer is set to GMT+5:30, the heatmap’s “days” align with that day boundary, and countdown timers show local time. Currently, Google’s Antigravity quotas are the same globally, so region-specific settings aren’t needed. (Enterprise/managed accounts may have custom quotas, which the extension will display as reported by the local server.)
Conclusion
Antigravity Usage Intelligence brings transparency to AI coding workflows. By breaking down token usage (fresh vs cache vs reasoning), showing daily trends, and syncing with your official quota, it turns Antigravity from a black box into an observable system. This helps you optimize performance (e.g. maximizing cache usage) and avoid surprises from hidden limits. Install it and let your usage data guide your AI development.
Learn more and get the extension on GitHub. Happy coding!
Suggested cover images:
-
cover-dashboard.png– "Developer’s dashboard showing AI token usage and quotas" -
cover-heatmap.png– "Calendar heatmap of activity (each square = token usage per day)" -
cover-tokens.png– "Diagram of token types (fresh vs cache vs output vs reasoning)" -
cover-coding.png– "Person coding with AI assistant (illustrates AI-driven development)" -
cover-architecture.png– "Architecture diagram of Antigravity data flow (local storage, language server, extension)"
Top comments (0)