Tokens from work you already ran
Remaining quota is one story. Token usage is the other: how much the sessions actually burned, on which models, at what estimated cost.
UsageAtlas turns supported local Codex session information into those aggregates. You can reopen a day instead of reconstructing it from a status line.
How to read the mix
Input, output, and cache behave differently on cost. A cache-heavy day can look loud in tokens and quieter in spend. The breakdown sits next to the headline so that does not surprise you twice.
Questions, answered
Can I view Codex token usage?
Yes. UsageAtlas shows tokens, requests, models, and estimated cost from supported local Codex activity.
Are token counts the same as credits?
No. Credits are a plan construct when Codex reports them. Tokens are activity. Both can appear in the dashboard.
Does this include other tools' tokens?
In the combined total, yes. Filter to Codex to hide them.