Open-source Codex usage trackers on GitHub, ranked

The open-source Codex usage tracker on GitHub that suits most people is UsageAtlas, a free desktop app under the MIT license that monitors Codex windows, reset times, tokens and estimated cost. CodexBar and ccusage are also on GitHub and are good fits for a Mac menu bar or a terminal report.

Why look on GitHub at all

People who search GitHub for a Codex tracker usually want three things: the code in the open, no account, and no fee. A usage tracker reads session files and signed-in tools on your machine, so being able to read what it does is a fair thing to ask for.

All three tools below are on GitHub. They differ in where they show the numbers and how much they watch for you.

1. UsageAtlas: desktop tracker with alerts

UsageAtlas is a local-first desktop dashboard. For Codex it reads the signed-in Codex CLI and shows:

• session and weekly windows with remaining capacity and reset times
• plan and credit details when Codex reports them
• tokens, requests and models from local session activity, with an estimated cost
• daily and historical views, model mix and time-of-day patterns

The monitoring part is the alert: set a threshold on a window and the app sends one desktop notification per reset cycle when you cross it. It also covers Claude Code, Cursor, OpenCode, GitHub Copilot and other coding tools in the same window.

Releases include installers for Windows, macOS and Linux. Local tracking needs no account, and prompts and responses are not read. Its cost figures are estimates, not a bill.

2. CodexBar: menu bar limits

CodexBar by Peter Steinberger is an MIT-licensed menu bar app for macOS 14 or later. Its README describes per-provider session, weekly and monthly windows with countdowns to the next reset. The GitHub page also lists a Linux desktop app and CLI builds for macOS and Linux. It is a good pick if you want limits in the Mac menu bar and little else on screen.

3. ccusage: terminal reports

ccusage is a command line tool. For Codex it reads session JSONL files under CODEX_HOME, which defaults to ~/.codex, and prints token usage and estimated cost with ccusage codex daily, monthly or session. Its docs mark Codex log support as experimental. It suits scripted reports, since each view can output JSON.

At a glance

Which one to install

Pick UsageAtlas if you want a tracker that keeps watching, stores history and works on any desktop system. Pick CodexBar if you live on a Mac and only want the reset countdown in the menu bar. Pick ccusage if you prefer piping reports into scripts. The tools do not conflict, so running UsageAtlas next to a terminal reporter is fine.

A note on accuracy

Every tracker here depends on what Codex exposes locally or through the signed-in CLI, and that can change when OpenAI updates the tool. For billing questions, the usage page in your ChatGPT account at chatgpt.com/codex/settings/usage is the source of truth, and /status in the CLI shows the current limits inside a session.