See the windows before a long task
Codex exposes session and weekly windows. A tracker is useful when you can see remaining room without leaving the work. UsageAtlas shows the supported windows, remaining capacity, and reset times.
That is the difference between guessing whether a refactor will fit and knowing you are already close to a weekly cap. How to check Codex usage covers the CLI path too.
Tokens, credits, and history
Limits answer whether you can keep going. Local activity answers what Codex actually did. UsageAtlas reads supported session information already on this computer and turns it into tokens, requests, models, and estimated cost.
When Codex reports plan or credit information, that sits beside the local activity. For a screen-oriented view, see the Codex usage dashboard.
Questions, answered
Can UsageAtlas track Codex CLI usage?
Yes. Supported windows, remaining capacity, reset times, credits where reported, and local session activity.
Does this replace Codex /status?
No. /status remains the in-CLI check. UsageAtlas adds history, estimated cost, alerts, and other tools.
Is UsageAtlas only for Codex?
No. Claude, Cursor, and OpenCode are supported sources in the same app.