How to check Codex CLI token usage and limits
On this page
Run /status in an active Codex CLI session to see where you stand, or open the usage dashboard at chatgpt.com/codex/settings/usage for current limits and reset times. Neither one tells you which skill or session used the tokens. For that, SkillKeeper reads the session logs Codex keeps on your Mac and splits tokens by skill and by session.
We make SkillKeeper. What follows about Codex comes from the Codex pricing docs and the Codex command reference, checked on 2026-10-14.
How Codex usage limits work
On ChatGPT plans, Codex usage is counted against a plan allowance. The pricing page describes per-five-hour estimates on some plans, a weekly limit that may also apply, and an allowance that local messages and cloud tasks share. Model choice, task size, reasoning, tool use and caching all change how fast it is used, and the page stresses the numbers are estimates, not fixed message limits. The docs say to check the dashboard for current limits and reset times, and they do not spell out how resets work, so use the dashboard rather than a number from a blog post.
Once included usage runs out, credits can pay for more on eligible plans.
Ways to check
| You want | Use |
|---|---|
| Limits and reset times for your plan | The usage dashboard at chatgpt.com/codex/settings/usage |
| A quick look inside a session | /status in the Codex CLI |
| Which skill or session used the tokens | A tool that reads the local logs, such as SkillKeeper |
What SkillKeeper shows for Codex
Codex keeps a log of every session under ~/.codex/sessions/. SkillKeeper reads those files on your Mac and shows:
- Tokens by skill. A skill counts when the agent reads its
SKILL.md. Sort the Skills tab by usage to see which ones are used and which never run. - Tokens by session. A session is one log file, named after the working folder, so you can tell which project took the tokens.
- Time windows and a chart. The last 5 hours, 24 hours, week and month, with hover showing each row's share. The last 5 hours and 24 hours are free; week and month need the $19 one-time license.
For Codex, SkillKeeper has no breakdown by agent or MCP server, and the limit gauge in the header is for Claude Code only. It works with one tool at a time: you pick Codex in the AI Tools and Folders setup.
Nothing leaves your Mac. The app reads local logs, and only anonymous usage counts are sent. See the privacy page.
If you also use Claude Code
Claude Code gets the full breakdown by skill, agent, tool, MCP server, memory file and session, plus your 5-hour and weekly limit: Claude Code usage monitor for Mac. The checking options for Claude Code are in how to check Claude Code token usage.
For other tools, see Gemini CLI token usage and Cursor token usage. To compare SkillKeeper with a command-line tool that also reads Codex logs, see SkillKeeper vs ccusage.
Checked on 2026-10-14. Limits and plans change often; if something here is out of date, tell us.