Your token report card
Other tools print a table. Token Forest grows a tree — and keeps the receipts.
Growth, usage and cost analytics for Claude Code & Codex — computed locally, priced offline, never uploaded.
🔒 Local-first · Log-only · No telemetry · Leaderboard off by default
UI shown is a demo · numbers are fictional examples · hover to pause
Inside the dashboard
Three views, one set of numbers — tree, charts and receipts always agree.
A profile for every tree: stage, days planted, growth curve — and what it's worth so far.
Full local analytics: daily, weekly and monthly charts, per-model splits for Claude & Codex, a 26-week heatmap, burn rate, per-project breakdown.
One line per conversation: title, project, prompts, all four token types, estimated cost.
Why it's different
Your stats grow on a tree — numbers you raised, not rows you scroll.
One line per conversation: what it was, which project, what it cost.
The official price table ships inside the app. Zero network at runtime — not an option, the only mode.
Four token types priced separately, cache reads at 0.1× with the math shown — the same accounting the official quotas use.
Three steps to the dashboard
Install and a tree is planted — it starts growing with every token you spend.
Keep using Claude Code / Codex. Nothing to configure, nothing to change.
Opens in its own resizable window — growth, usage and conversations, any time.
The math, in plain words
How the numbers are computed — up front.
Why are my cache reads in the billions?
That's how agents work: every tool call re-reads the conversation prefix. It's also the cheapest type (~0.1× input) — the dashboard prices it at 0.1× and lists it separately.
Are the cost numbers accurate?
They're estimates: local usage × a bundled official price table (with its update date). Not a bill; subscription discounts not included.
Does any data leave my machine?
By default, no. The dashboard uses metadata only — token counts, model names, timestamps, session titles — never conversation content, all shown locally. The optional leaderboard (off by default) syncs only the fields listed in its consent dialog: an anonymous ID, display name, region, and per-tree token totals and growth stages.
How far back does history go?
First open re-parses all local logs (even from before you installed), then a local ledger takes over — your history survives the CLI's 30-day log cleanup.
Uses only metadata — token counts, model names, timestamps, session titles. Conversation content is never stored or uploaded.
Costs are estimates from a bundled price table, not a bill.
