All UsageAtlas guides

New supported tools

Track Antigravity CLI, Pi / OMP, and Muse Code usage

UsageAtlas now tracks local history for Antigravity CLI, Pi / OMP, and Muse Code. Learn which tokens, sessions, and cost estimates each integration supports.

Quick answer

UsageAtlas now supports local usage history for Antigravity CLI, Pi / OMP, and Muse Code, alongside Codex, Claude Code, Cursor, and OpenCode. Track recorded tokens, requests, models, and sessions without a UsageAtlas account. Supported session files must exist on the same computer.

Download app to track this on your machine

Antigravity CLI usage

UsageAtlas reads supported Antigravity CLI SQLite conversation histories. You can see recorded input, cached-input, and output tokens, requests, models, and sessions. Estimated cost appears when model pricing is known.

Antigravity support is CLI-only. The IDE's .pb conversation files are not supported, and this integration does not collect subscription quotas, balances, or reset times.

Pi and Oh My Pi usage

Pi and Oh My Pi share the Pi / OMP source in UsageAtlas. The reader collects tokens, requests, models, sessions, and available project information from supported local JSONL histories. Anthropic and OpenAI Codex usage formats are currently supported.

Cost uses known model prices to estimate API-equivalent usage. It does not represent your subscription charge. Other backend formats may leave history incomplete, and unknown model prices remain unavailable. Pi / OMP does not add subscription limits.

Muse Code usage

Muse Code adds token, request, model, and session history from supported v1 session.jsonl files. Input, cache, and output counters contribute to your usage totals when the records contain valid counts.

Muse Code dollar costs are unavailable in this integration. Its subscription limits, balances, and reset alerts are also not collected. Missing data does not mean zero usage or free usage.

Get the new sources to appear

  1. Use a supported tool locally so it creates session history.
  2. Open the latest UsageAtlas build on that computer and refresh usage.
  3. Check Settings → Sources, then use the tool filter in Today or History.

Installation alone is not enough. UsageAtlas automatically enables a source when it detects supported history. You can enable a source manually in Settings, but unreadable or unsupported files still cannot provide usage statistics.

Default locations include ~/.gemini/antigravity-cli/conversations for Antigravity CLI, ~/.pi/agent/sessions and ~/.omp/agent/sessions for Pi / OMP, and ~/.local/share/muse/sessions for Muse Code. Custom-directory options are listed in the local provider documentation.

Coverage depends on readable, compatible records. Unsupported schemas, malformed files, or scan limits can produce partial history. These integrations have automated parser coverage; live testing across all three operating systems is still pending.

Questions, answered

Does UsageAtlas track Antigravity IDE usage?

Not yet. Antigravity support currently reads supported CLI SQLite histories. IDE .pb histories are not supported.

Does Pi / OMP support every model backend?

The current reader supports Anthropic and OpenAI Codex usage formats in local Pi / OMP sessions. Other backend formats are not guaranteed and may produce partial history.

Do these sources show subscription limits or billed costs?

No subscription limits or reset alerts are collected for these three sources. Antigravity CLI and Pi / OMP can show API-price estimates when pricing is known. Muse Code cost remains unavailable.

Why is a new source missing from my tool filter?

The filter shows enabled sources. Automatic detection needs supported local history or saved usage. Check Settings → Sources and confirm the tool has written compatible session files on this computer.