Quick answer
UsageAtlas groups local Claude Code, Codex, OpenCode, and Pi / OMP history by project, with tokens and estimated cost for each. Open History, pick a range, and sort by project to find the repository that used the most.
See usage by project
- Install UsageAtlas on the machine where you code.
- Open History and choose 7, 30, or 90 days.
- Look at the project breakdown for tokens and estimated cost.
Projects come from the working folder your tool recorded. The project names stay on your computer and never enter cloud saves.
Billing clients for AI usage
If you pass AI costs to clients, a per-project estimate is a fair starting point. It is an API-price estimate, not your subscription bill. On a flat plan, use it to split the plan cost by share of usage instead.
What is not per project
Usage windows and credit balances belong to the account, not a folder. Cursor and the credit-based tools do not report projects, so their usage stays in the tool totals.
Questions, answered
Can I see Claude Code usage by project?
Yes. UsageAtlas reads the project folder from Claude Code's local history and groups tokens and estimated cost by it.
Are project costs exact?
No. They are estimates from token counts and known model prices. Your plan or invoice is the real number.
Do project names go to the cloud?
No. Cloud saves keep opaque identifiers and leave out project names and file paths.