Quick answer
Oh My Pi stores each conversation as a local session file under its data directory, grouped by project. The CLI can list and resume recent sessions; for older ones, read the files directly or point a local tracker at the folder, which also gives token totals per session.
The layout
| Level | What it holds | Why it matters |
|---|---|---|
| Data directory | All sessions for the user | Back up this folder |
| Project folder | Sessions for one repository | Per-project cost |
| Session file | Turns, model, tokens | One task's record |
| Metadata | Timestamps and model IDs | Grouping and rates |
Folder names follow the CLI's own convention and can change between releases. Confirm against the current documentation rather than an old path from a blog post.
List and resume
- Run the CLI help to find the session subcommand.
- List recent sessions and note the identifier.
- Resume the one you need, or open the file directly.
- Copy the file before editing it by hand.
omp --help\n# look for a sessions or resume command\nomp sessions listRead without opening every file
Reading JSON by hand is fine for one session and painful for a month. UsageAtlas parses the folder and reports tokens per session, per model, and per day, which is the same data with the arithmetic done.
For the token view, see Pi and OMP token usage. For setup, see how to track Pi and OMP usage.
Questions, answered
Where does Oh My Pi store sessions?
In a data directory under your home folder, grouped by project. The exact path depends on platform and version.
Can I resume an OMP session?
Yes, the CLI provides session listing and resume. Check its help output for the current command names.
Can I delete old OMP sessions safely?
They are local history, so deleting them removes your only record of that usage. Archive rather than delete if you track cost.
