# How to track Pi and Oh My Pi token usage

> Source: <https://usageatlas.com/guides/how-to-track-pi-omp-usage>
> Published: 2026-09-30 00:00:00+00:00

## Track Pi and OMP sessions

1. Run Pi or Oh My Pi locally to create session logs.
2. [Install UsageAtlas](https://usageatlas.com/#download) 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](https://github.com/SRX9/UsageAtlas/blob/main/docs/LOCAL_PROVIDERS.md) 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.