02 / codex-spend · local usage dashboard
Your Codex usage is already on disk.
One command turns local Codex state into a private dashboard for tokens, estimated cost, cache use and project activity.
The problem
Long Codex sessions make usage hard to reason about. The raw data exists, but it is split between SQLite state and session logs. I wanted a quick answer without sending that history to another service.
What I built
- Reads the latest Codex state database and session logs
- Breaks usage down by day, model and project
- Accounts for cached input and reasoning tokens in cost estimates
- Runs a dashboard on 127.0.0.1 and uploads nothing
- Supports subscription-plan mode alongside API pricing
Why it stays local
No account, upload or hosted database. Run npx codex-spend and the browser opens locally. That choice keeps setup short and private usage data on the machine.
Dependency: the parser follows Codex's local formats and needs the sqlite3 command. Format changes can require an update.