Quick answer
Tracking every tool in one place means reading each tool's local session data rather than its website. UsageAtlas reads 14 providers on your machine, shows reported plan usage and resets where the provider exposes them, and keeps 7, 30, or 90 days of token history without sending prompts anywhere.
What gets covered
| Category | Providers | Data source |
|---|---|---|
| First-party agents | Codex, Claude Code, Copilot | Local logs plus reported quota |
| Editors | Cursor, Qoder | Reported plan usage and credits |
| Local-first CLIs | OpenCode, Pi/OMP, Muse Code, Antigravity CLI | SQLite or JSONL sessions |
| Metered tools | Warp, Kimi, Kilo, Factory, Amp | Reported balances and quotas |
Fourteen providers in one list, with the same definitions for input, output, cached, and reasoning tokens where the tool records them.
Set it up in five minutes
- Install UsageAtlas for your platform.
- Use your tools normally so sessions exist on disk.
- Open the app and confirm which providers were detected.
- Connect the ones that need a key or account, such as Kimi or Qoder.
- Open Today, then switch to History for the 30-day view.
Anything not detected is almost always a path issue. The not showing checklist covers the fix per platform.
What to look at each week
- Which tool is closest to its limit.
- Which project consumed the most tokens.
- Whether one model accounts for most of the spend.
- Whether an alert fired and why.
- Whether the total rose without more work.
Five minutes a week beats an hour at invoice time. The daily tokens benchmark gives you a reference for what normal looks like.
Questions, answered
Can I track every AI coding tool in one app?
UsageAtlas covers 14 providers in one desktop app by reading local session data and provider-reported balances. Tools it does not support stay in their own console.
Does one dashboard need all my API keys?
Only for providers that report usage through an account, such as Kimi or Qoder. Local session readers need no key at all.
Is the dashboard cloud-based?
No. It runs locally. Cloud sync is optional and separate, and local tracking needs no account.