Repository navigation
Feat: Add OMP Directory Support #1193
Description
What do you want to change?
Auto-detect OMP (oh-my-pi) sessions at ~/.omp/agent/sessions in the pi adapter.
Why?
OMP is one of the most widely used forks of pi (~8.7k stars on GitHub). It writes identical JSONL session files with the same message.usage schema. Currently, if a user of OMP wants to use ccusage, it will error with "No usage data found" despite OMP using pi under the hood. They must use ccusage pi with --pi-path ~/.omp/agent/sessions.
How? (optional)
Add ~/.omp/agent/sessions as a fallback default path in paths.rs for pi when the standard ~/.pi/agent/sessions doesn't exist or is empty.
Reacted by Bohdan Zhuravel, sgfeniex, Robbie Blaine, RedlicaDev, Shohei Fujii and dylxc
Activity
github-actions commentedon May 30, 2026
This issue was auto-closed. Issues from new contributors are auto-closed by default.
Maintainers review auto-closed issues and reopen worthwhile ones. Issues that do not meet the quality bar in CONTRIBUTING.md may not be reopened or receive a reply.
Keep the issue short, concrete, and written in your own voice.
If a maintainer replies
lgtmi, your future issues will stay open. If a maintainer replieslgtm, your future issues and PRs will stay open.See CONTRIBUTING.md.
ryoppippi commentedon Jun 4, 2026
@tgrundler please send a pr. i think it shouldn't be big
sgfeniex commentedon Jun 18, 2026
Since finding PI_AGENT_DIR, I don't have a problem. I wouldn't mind if my PR was rejected.
ShawnFumo commentedon Jul 14, 2026
Just a quick note to anyone else searching for this issue: you can also add this config file instead of setting an env variable
{ "$schema": "https://ccusage.com/config-schema.json", "pi": { "stores": [ { "name": "omp", "path": "~/.omp/agent/sessions" } ] } }ryoppippi commentedon Aug 31, 2026
Historical audit: this discussion was auto-closed by the legacy contributor gate. That closure did not assess technical importance.
Audit result: resolved. A later merged change or the current
mainimplementation covers this request. This item is kept for history and does not need to be reopened.