Quick answer
Pi and Oh My Pi store conversations as local session files that include the model and token counts per turn. UsageAtlas reads both formats and reports daily, per-model, and per-project totals. No account is needed, and nothing leaves the machine unless you enable optional sync.
One reader for both
| Tool | Session store | What the tracker reads |
|---|---|---|
| Pi | Local session files | Model, tokens, timestamps |
| Oh My Pi (OMP) | Local session files | Same fields, OMP format |
| Both | Per-project folders | Working directory when present |
| Editor status bar | Current context | Not historical |
Track it
- Install UsageAtlas.
- Use Pi or OMP as usual to create sessions.
- Confirm the app detected the session directory.
- Check Today for the live session and model.
- Use History for 7, 30, or 90-day totals.
Why local history matters here
Pi and OMP are local-first tools. Their session files are often the only record of what a task consumed, because there is no vendor dashboard aggregating your usage. If you delete the folder or rebuild a container, the history is gone.
- Back up the session directory with your dotfiles.
- Keep one machine as the source of truth for a project.
- Export aggregates rather than transcripts when sharing.
- Track daily so a runaway context is caught in a day, not a month.
The OMP sessions guide covers listing and reading sessions directly, and how to track Pi and OMP usage has the setup steps.
Questions, answered
Does Oh My Pi report token usage?
Its local session files record model and token data per turn, which a local tracker can read.
Does UsageAtlas track Pi and OMP separately?
Yes. Both are supported providers, and you can compare them in the same History view.
Is there a Pi usage dashboard online?
Not a vendor one. Local tracking is the practical route, because sessions live on your machine.