ccusage for Codex: what it shows and what a dashboard adds

Yes, ccusage works for Codex: run npx ccusage@latest codex daily and it prints Codex token use and estimated cost by day from the files Codex keeps on your machine. If you also want your remaining Codex windows, reset times and a history you can scroll, UsageAtlas shows them in a free desktop app.

Three ways to read Codex usage

Codex users tend to end up with three tools for three questions.

1. /status inside Codex. OpenAI's docs describe it as showing session configuration and token usage. It is the fastest check while you work, and it covers the session in front of you.
2. ccusage in a terminal. A report across days, weeks or months, built from local Codex data.
3. UsageAtlas on the desktop. Windows, credits, history and your other coding tools in one view.

Using ccusage for Codex

The name points at Claude Code, but ccusage now reads many coding CLIs, Codex among them. The focused commands follow one pattern:

• ccusage codex daily for a day-by-day table
• ccusage codex weekly or monthly for longer views
• ccusage codex session to group by session
• --json to hand the numbers to a script, --since and --until for a date range

Drop the codex word and ccusage reports every source it detects in one table, which is handy if you also use Claude Code or OpenCode. It needs no install when you use npx or bunx, and it is free under the MIT license.

What it does not try to be is a dashboard. You get a table when you ask for one, and the cost column is an estimate built from token counts and model prices, not a figure from your OpenAI account. If you only care about tokens, --no-cost hides the cost columns.

Using UsageAtlas for Codex

UsageAtlas is a local-first desktop app. It connects through the Codex CLI you are already signed into and shows:

• session and weekly usage windows, with reset times
• plan and credit details where your account reports them
• local token, request and model history, with cost estimates

The same window holds Claude Code, Cursor, OpenCode and other tools, so a day split between Codex and Claude Code adds up to one total. You can set a threshold and get a desktop alert once per reset cycle when a window passes it.

It is free and open source, needs no account for local tracking and does not read prompts or responses. Cost numbers are estimates, not your OpenAI bill.

Which one to reach for

Is UsageAtlas "ccusage-codex"?

No. People sometimes search for a "ccusage-codex" app and land on UsageAtlas. It is a separate project with its own adapters, not a fork or a wrapper around ccusage. You can keep running ccusage in the terminal and open UsageAtlas when you want the picture rather than the printout.

For most Codex users the practical setup is simple: /status for the moment, UsageAtlas for the week, and ccusage when a script needs the numbers.