aiburn
Fast, fully local usage & cost reporting for Claude Code and Codex, in one table. See how much you're burning on your coding agents.
$ aiburn
aiburn · Claude Code + Codex usage
Date Agent Models Input Output Cache Cost
────────── ────── ─────────── ───── ────── ───── ──────
2026-07-20 claude opus-5 2.81K 222K 24.4M $20.44
codex gpt-5.6-sol 64.0K 2.42K 500K $0.64
2026-07-21 claude opus-5 127 84.8K 22.3M $17.27
────────── ────── ─────────── ───── ────── ───── ──────
Date Agent Models Input Output Cache Cost
TOTAL 66.9K 309K 47.2M $38.35
Claude $37.71 47.0M tokens
Codex $0.64 567K tokens
Total $38.35
Scanned 214 files in 61ms
Each raw model gets its own row, with repeated date and agent labels suppressed
so model-level comparisons stay readable.
Token counts are compact (K/M/B/T) and costs exact — pass --exact for
full counts, or --json for raw integers. JSON groups mirror the table: one
object per (date/month, agent, model), with the raw model name in models.
Why aiburn
- Fully local & private — it only reads the log files and local Codex config your agents already write on your machine. No network calls or account; nothing about your usage ever leaves your computer.
- One command, no install —
uvx aiburnon macOS or Linux. - Both agents, one view — Claude Code and Codex side by side, by day, month, or session.
- Fast at any size — scans gigabytes of history in well under a second, with near-instant startup, so it stays snappy as your logs grow.
- Accurate cost — recomputed from token counts (including cache tiers), with date-aware model aliases and Codex Standard/Fast/Priority pricing.
Run it
No install needed — uv fetches a prebuilt binary and runs it:
uvx aiburn # macOS / Linux, any arch
uvx aiburn monthly
Keep it as a permanent command:
uv tool install aiburn # then just `aiburn`
Or build from source with a Rust toolchain:
cargo install --git https://github.com/handasontam/aiburn
Usage
aiburn [command] [options]
Commands:
daily Per-day usage and cost (default)
monthly Per-month usage and cost
session Per-session usage and cost
Options:
--since <YYYY-MM-DD> Only include usage on/after this date
--until <YYYY-MM-DD> Only include usage on/before this date
--claude Only Claude Code
--codex Only Codex
--all Show every session (session view; default: top 25)
--exact Full token counts instead of K/M/B/T
--json Emit JSON instead of a table
-h, --help Show this help
-v, --version Show version
What it reads
Only your local coding-agent logs — read in place, never sent anywhere:
- Claude Code —
~/.claude/projects(also~/.config/claudeand$CLAUDE_CONFIG_DIR) - Codex —
~/.codex/sessionsand~/.codex/archived_sessions, plus the top-levelservice_tierin~/.codex/config.toml(or$CODEX_HOME)
A file that cannot be opened or read to the end is counted in the footer rather than silently skipped, so a permissions problem shows up as a warning instead of a smaller total.
Cost accuracy
Costs are recomputed from token counts with a built-in, pinned public pricing
table, including Claude's 5-minute and 1-hour cache tiers and per-model cache
rates (Fable 5.1 reads cache at $0.25/MTok and Opus 5.5 at $0.20/MTok, not the
usual 10% of input).
Claude Code figures match ccusage's to the cent; ccusage's headline total will
still be higher if it also finds OpenCode, Gemini, or other agent logs that
aiburn does not read. Codex logs carry no authoritative cost, so aiburn uses
public list pricing: explicit priority/fast events use the matching Fast
rate, missing tiers follow the top-level Codex config, and unknown tiers fall
back to Standard. A Codex request whose whole context (fresh plus cached input)
exceeds 272K tokens is billed entirely at OpenAI's long-context tier, as
ccusage does.
Two details worth knowing:
- Fast mode costs more per token. Fast/Priority usage appears as its own
-fastrow for both agents, priced at the per-model premium rate where one is published; otherwise at the base rate, which undercounts rather than dropping the row. - Codex replay history is skipped. Forking or resuming a session copies the parent rollout's records into the new file; those replayed token events belong to the parent's own file and are not charged again.
Acknowledgements
Inspired by ccusage by @ryoppippi and contributors — a great, broader tool that covers many more agents. aiburn is a smaller reimplementation focused on just Claude Code + Codex. ccusage is MIT licensed.
License
MIT
Metadata
Release files for aiburn 0.4.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| aiburn-0.4.5-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details for aiburn-0.4.5-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| aiburn-0.4.5-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details for aiburn-0.4.5-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
| aiburn-0.4.5-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for aiburn-0.4.5-py3-none-macosx_11_0_arm64.whl |
| aiburn-0.4.5-py3-none-macosx_10_12_x86_64.whl | Python 3 | none | macOS 10.12+ x86-64 | Details for aiburn-0.4.5-py3-none-macosx_10_12_x86_64.whl |
Total release size: 1.1 MB
Release files / aiburn-0.4.5-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | aiburn-0.4.5-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 299.0 kB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
4f8e69e89d3b771df3e5db54361b210d4d7a60887650f7cdcbb405dacfd88bfc
|
|
BLAKE2b-256 checksum How to use checksums |
21bb15f92a3f31526b8c3d4b03ec858ac7552a4d688f70654424566818319350
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / aiburn-0.4.5-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | aiburn-0.4.5-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 283.1 kB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
82827b674558c68ed07bacbd7fddd81bba6c6944dc7eeffa3e49845307721a01
|
|
BLAKE2b-256 checksum How to use checksums |
ac21c84e07d5ca27369921f38a36da9a5ce4de86b5896ad283fedfbb52408164
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / aiburn-0.4.5-py3-none-macosx_11_0_arm64.whl
| Download URL | aiburn-0.4.5-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 256.9 kB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
98ab1c16e58d7869ea977a46e03c816b0be17c253d4eed6fccc57969d74c8038
|
|
BLAKE2b-256 checksum How to use checksums |
b1a218056c68de0bca84b552413c0d73504cc28ba274cf9a289d9315042f19f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / aiburn-0.4.5-py3-none-macosx_10_12_x86_64.whl
| Download URL | aiburn-0.4.5-py3-none-macosx_10_12_x86_64.whl |
|---|---|
| Size | 273.7 kB |
| Tags | Python 3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
3323bf5e77a6f22703f7a7611f67d6e020cf8d383b74c9aa36c7c6004053e8f6
|
|
BLAKE2b-256 checksum How to use checksums |
02978e81dcd4fcc48c7ca697d9c2f9fe8e41ad659319d254b4270e5269cc306a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logSecurity for aiburn 0.4.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 4 files in this release have been uploaded with provenance metadata.
Attestation for aiburn-0.4.5-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.