🔥 TokenBurn

See what your AI coding agents cost you — in tokens and dollars, from the logs already on your disk.

A terminal UI, a desktop GUI and a web dashboard (plus a CLI for scripts), all in Rust, all showing the same live numbers.

TokenBurn reads local logs only — no network calls, no account, no telemetry. It understands pi, Zed, Claude Code, Codex, Copilot CLI, Gemini CLI, OpenCode and Amp, shows where the tokens (and money) went, and keeps itself up to date while you work.

Choose your front-end

Same data, same charts, same 43 themes — pick whichever fits how you work.

🖥️ Terminal UI — tokenburn-tui

For when you live in the terminal. Browse the report, watch the charts, and filter as you type.

• Report table with a stacked token chart and a share-by-project pie
• Instant filtering: / free text (claude -zed), f per-tool checkboxes with row counts
• Options popup (o): toggle panels, auto-refresh interval (5–300 s or off)
• Theme picker with live preview (T), or [ / ] to cycle

cargo install tokenburn-tui && tokenburn-tui --daily

🪟 Desktop GUI — tokenburn-gui

A native window (Iced) with interactive, animated charts. Click a bar to scope everything to that day, click a slice to scope it to that project.

• Stacked bars over time (tokens or cost) and a project donut; hover for tooltips
• Click to drill down — the table, totals and the other chart follow
• macOS app, Windows installer, and Linux (one binary for X11 and Wayland)
• Drop-down pickers for tool, view, window and theme

cargo install tokenburn-gui && tokenburn-gui

🌐 Web dashboard — tokenburn-web

A local web page in your browser. Live over a WebSocket, drill-down by clicking, and every view is a shareable URL.

• Server-rendered SVG charts with CSS animation — no JavaScript charting library
• Filters are Topcoat signals: changing one updates the page in place
• A drilled-down view is part of the URL: ?sel_bucket=2026-09-22&sel_project=pi%3Aatlas
• JSON API at /api/report; binds to 127.0.0.1 by default

tokenburn-web            # opens http://127.0.0.1:3000

⌨️ CLI — tokenburn

For scripts and pipes.

tokenburn                  # this month, every tool, with a per-tool breakdown
tokenburn --daily --all    # all history, one line per day and tool
tokenburn --tool claude --monthly
tokenburn --json           # machine-readable

What it reads

all (the default) reads every tool that is installed; one that isn't simply contributes nothing. Cost is shown only where the tool logs one — otherwise $0.0000 rather than a guess (token counts are exact). Cursor, Windsurf, VS Code Copilot Chat and JetBrains AI keep no usable token log on disk, so they can't be supported.

The Claude Code, Codex, Copilot CLI, Gemini CLI, OpenCode and Amp readers follow the formats documented by ccusage and are covered by fixture tests; pi and Zed were also checked against real logs. If one misreads your data, open an issue with a (redacted) log line.

Per-platform locations and the full list of overrides are in Platform support.

Shared by every front-end

Always up to date. Nothing to press — each front-end re-reads the logs itself, and only re-parses the files that changed, so leaving one open is cheap.

Charts. Tokens or cost over time (one stacked bar per hour, day or month, one colour per tool) and a donut of the biggest projects. In the GUI and web dashboard they animate in, and clicking drills down:

Changing the tool, view or window drops the selection.

43 themes, dark and light — Dracula, Nord, Tokyo Night, Catppuccin, Gruvbox, Solarized, Kanagawa, Rosé Pine, Everforest and more — shared by every front-end, including one colour per tool in the charts. Pick one with --theme "Tokyo Night" (--list-themes lists them), or in the UI; the choice is remembered in settings.json (~/.config/tokenburn/, ~/Library/Application Support/tokenburn/, %APPDATA%\tokenburn\; override with TOKENBURN_CONFIG_DIR), so all front-ends start with the same theme.

Install

Prebuilt (GitHub / Gitea releases)

Every portable archive holds all binaries for that target, the web runtime in assets/ (so tokenburn-web runs live), the README and licence, plus a .sha256.

macOS: the app is ad-hoc signed, not notarised — right-click → Open the first time, or xattr -dr com.apple.quarantine TokenBurn.app.

From crates.io

cargo install tokenburn        # CLI
cargo install tokenburn-tui    # terminal UI
cargo install tokenburn-gui    # desktop GUI
cargo install tokenburn-web    # web dashboard (static mode; see "Live mode" below)

No python3 or zstd binary needed — sqlite and zstd are bundled.

Using it

TUI keys

Filters apply instantly to the rows already loaded; the header shows what is active, e.g. ⌕ filter:"claude" tools:3/8 412/3,029 rows.

Web dashboard

just run-web                        # live dashboard, opens http://127.0.0.1:3000
tokenburn-web --port 8080 --no-open # flags: --host, --port (or HOST / PORT), --no-open, --theme

It binds to 127.0.0.1. --host 0.0.0.0 exposes it on the network — there is no authentication, and token/cost data is private, so only do that deliberately.

Live mode needs Topcoat's browser runtime. Release archives, the DMG, the Windows installer and the .deb/.rpm include it. When building yourself, just run-web bundles it (needs cargo install topcoat-cli), or run topcoat asset bundle and point TOKENBURN_WEB_ASSETS at the result. Without it, tokenburn-web still works and serves a static dashboard (form filters, links instead of clicks, reload every 10 s) — which is what cargo install tokenburn-web gives you. Search order: $TOKENBURN_WEB_ASSETS, <exe dir>/assets, <exe dir>/../share/tokenburn-web/assets, /usr/share/…, /usr/local/share/….

Platform support

macOS, Linux and Windows, all four binaries:

Log locations are found per platform; every one can be overridden:

Linux notes

• One GUI binary serves X11 and Wayland. It links only libc/libm and loads X11, Wayland, xkbcommon and the GPU libraries at runtime. It picks Wayland when WAYLAND_DISPLAY is set; force X11 with env -u WAYLAND_DISPLAY tokenburn-gui.
• Software rendering is the automatic fallback without a usable GPU (VMs, remote desktops); force it with ICED_BACKEND=tiny-skia.
• glibc builds (AppImage, .deb, .rpm, *-gnu) are linked on Ubuntu 22.04, so they need glibc ≥ 2.35. Static musl builds (CLI, TUI, web) run anywhere — Alpine, containers, NixOS.
• The GUI needs libxkbcommon and fonts, as any desktop Linux has.

Development

just build              # whole workspace
just run-tui            # run-cli / run-tui / run-gui / run-web
just check-all          # fmt + clippy + tests + nu script tests
just coverage           # line coverage (cargo-llvm-cov)
just --list             # everything else

tokenburn (cli) ──┐
tokenburn-tui ────┼──▶ tokenburn-core ──▶ rusqlite, zstd, serde_json, chrono
tokenburn-gui ────┤
tokenburn-web ────┘

Demo recordings

The GIFs above live in examples/vhs/generated/ and are stored with Git LFS (git lfs install once). They are generated from synthetic data (examples/vhs/fixture.sh), never from real logs:

just vhs-tui         # TUI + CLI tapes (examples/vhs/*.tape) — needs vhs, ttyd, ffmpeg
just screenshots     # GUI (macOS) + web screenshots and GIFs — needs ffmpeg, node, a Chromium browser
just vhs-tape filter # one tape

License

MIT — see LICENSE.