Tokentrail
Here be tokens
Three things, kept local
Tokentrail reads what Claude Code already wrote to disk, and turns it into a ledger you can navigate by branch, feature, and PR.
Every session's JSONL stays on your machine. Tokentrail reads them in place — never uploaded, never proxied, never seen by anyone but you.
Each token step gets tied to the Git branch you ran it on, the feature it touched, and the PR that merged it.
Spike days, hot sessions, and burning features get flagged automatically. Optional Notion sync mirrors your daily rollup for the team.
A guided checklist on first run
CLI, SwiftBar menubar widget, dashboard daemon, Claude Code skills, session-end hook, and a clickable Tokentrail.app launcher — installed one tick at a time, with the trail map building itself beside you as you go.
The wizard reflects live state — every box ticks itself as each piece lands.
Where the trail picks up each morning
Cost today, the week so far, sparklines per top feature, and a running list of every commit Tokentrail attributed since you last looked.
Real data from the local SQLite — no demo numbers, no remote calls.
Anomalies, surfaced before the bill is
Tokentrail flags spike days, hot sessions, and burning features automatically — pulled together on a single triage view so you don't have to grep your wallet.
Each row is a real signal from the local model — snooze, investigate, or jump straight into the feature.
Drill into any feature
Cost over time, a session-level breakdown, and the exact commits that finished the work. Topic clustering groups related sessions when transcripts overlap.
Branch ↔ feature ↔ PR — the same attribution chain, all the way down.
Tokentrail can mirror your daily rollup into a Notion database — one env var to enable, runs on the same daily cadence as tokentrail rollup. Setup lives in the README under Notion sync.