Codex Usage
Back to Codex Usage Overview
Local Developer Utility

Install Codex Usage

A free local tool that shows your 5-hour and weekly remaining Codex quota and reset times, in your terminal or a local browser dashboard.

Requirements

  • macOS
  • Python 3
  • Codex CLI installed
  • Already logged into Codex

Stop guessing your quota mid-refactor.

Codex Usage is a free local tool. It reuses your already-authenticated Codex CLI to show 5-hour and weekly remaining percentages and reset times, in your terminal or a local browser dashboard.

macOS
$curl -fsSL https://codexusage.dev/install.sh | sh
  • No separate account, OAuth, or API key
  • ~30-second install, no sudo
  • Local browser dashboard refreshes every 60s, plus a manual Refresh button
  • Runs locally; session tracking is in memory only, no telemetry sent back to us
codex-usage --weblocalhost
5h remaining78%
Weekly remaining64%
Auto-refreshevery 60s

Using It

Terminal view:

codex-usage

Local browser dashboard:

codex-usage --web
  • 5-hour quota shown as primary, weekly quota as secondary
  • Local browser dashboard auto-refreshes every 60 seconds, plus a manual Refresh button
  • Tracks usage change since the dashboard session started — kept in memory only, no persistent history
  • Runs on localhost; no codexusage.dev account or API key required

Pre-Install Questions

Does Codex Usage need sudo / root privileges?

No. The installer places the binary in your user directory and never requests administrative access.

How does it know my remaining quota?

It reuses the Codex CLI authentication already on your machine and reads the usage windows your authenticated Codex client reports — the same 5-hour and weekly numbers you'd see from /status.

Does it need an account or API key?

No. There's no codexusage.dev account and no OpenAI API key. It relies entirely on your existing Codex CLI login.

Does it store my usage history?

No. Session tracking (usage since the dashboard opened) is kept in memory only and resets when a new quota window is detected. Nothing is written to persistent storage.

Runs locally. Codex Usage itself keeps session tracking in memory only and sends no usage telemetry back to codexusage.dev. Codex itself still communicates with OpenAI using your existing authenticated login.