How to check your Codex usage

In the Codex CLI, type /status to see your remaining limits, or /usage to see token activity by day or week. Your account's usage dashboard has the current limits and reset times.

1. /status in the CLI

During a Codex CLI session, /status shows the current session's configuration, how much context capacity is left, and your remaining limits. It is the quickest check while you are working.

2. /usage in the CLI

/usage opens your account's token activity. You can jump straight to a view with /usage daily, /usage weekly or /usage cumulative.

3. The usage dashboard

The usage dashboard in your Codex account settings shows your current limits and when they reset. OpenAI's own advice is to check it every week or two to see your pace, because how much a message uses depends on the model and the size of the task.

4. A footer in the terminal

Codex has a /statusline command that lets you pick what the footer shows, including context and limits, and saves your choice.

5. The log files

Codex writes every session to ~/.codex/sessions/, in folders by date. Each model reply has a usage record with input, cached input and output tokens. Adding them up per file gives usage per session, which none of the views above show. One thing to know: the input figure already includes the cached part. More on reading Codex logs by session.

Which session used it?

The input figure on a session's latest reply is how much it re-reads on every turn. When that is large, the session is costing more per message than a fresh one would. In Codex, /compact summarises the conversation to free up context, and starting a new session for the next task frees all of it.

Cost Doctor reads the Codex logs and shows each session in your menu bar with its size per turn, alongside your Claude Code sessions if you use both. Its Codex totals were checked against a separate count of the same log files and matched exactly.