UsageAtlasBeta
Sign inGitHubOpen source
All UsageAtlas guides

Pi and Oh My Pi token usage

How to track Pi and Oh My Pi token usage

See Pi and Oh My Pi tokens, models, sessions, and available cost estimates in UsageAtlas, a free, open-source desktop usage tracker.

Quick answer

UsageAtlas groups Pi and Oh My Pi under Pi / OMP. It reads supported local session logs for tokens, models, requests, projects, and session history, with API-price estimates where pricing is known. The app is free and open source.

Download UsageAtlas for free

Free and open source for Windows, macOS, and Linux. No UsageAtlas account needed. View the source on GitHub.

Track Pi and OMP sessions

  1. Run Pi or Oh My Pi locally to create session logs.
  2. Install UsageAtlas on that computer and check Pi / OMP in Settings → Sources.
  3. Refresh, then select Pi / OMP in Today or History to inspect recorded activity.

Find your session directory

Pi commonly stores JSONL sessions under ~/.pi/agent/sessions; OMP uses supported stores such as ~/.omp/agent/sessions. UsageAtlas also discovers supported OMP profiles. For a custom root, start the app with PI_CODING_AGENT_SESSION_DIR set to that directory. See the supported locations for the complete list.

Check backend coverage

The current reader supports Anthropic and OpenAI Codex usage formats. Other backend records can leave history partial. Recorded input, cache, and output tokens stay under Pi / OMP, even when the model comes from another company. Known prices produce API-equivalent estimates; the reader does not collect subscription quotas.

Questions, answered

Does Pi usage also count under Codex or Claude?

Pi events stay under Pi / OMP. UsageAtlas's Codex and Claude readers do not scan Pi session roots.

Does the estimated cost equal my subscription bill?

No. It estimates the API value of recorded tokens using known model prices. Subscription charges are separate, and unknown prices remain unavailable.