tareClaude Code skill that reads your local session logs and answers 'where did my tokens go' in plain English: deduplicated totals, cost charged to the tool that caused it, 5-hour window state.
Why switchBoth are local-first cost ledgers built from session files already on disk. Codeburn spans 36 tools for breadth; tare goes deep on one — causal attribution and rolling-window forensics that only work if you model a single harness's log format precisely.
Full comparison → agentacctLocal-first work receipts for coding agents: reads the session logs Claude Code, Codex, OpenCode and Hermes already write and reports what each task did, what it cost, and whether a check proved it.
Why switchNearest neighbour and a clean split. Codeburn is a local-first cost ledger — tokens and dollars broken down by task, model and project from 36 tools' session files. Agentacct reads the same logs but reports the work and its evidence, and will not call a task verified without an independent check.
Full comparison → ai-token-monitorMenu-bar/tray app for macOS and Windows that reads Claude Code, Codex and OpenCode session logs and shows live token spend — per-model pricing with cache reads, plan-limit bars, webhook alerts.
Why switchSame job — watch AI coding spend from local session logs — at different scope: ai-token-monitor is a tray app covering Claude Code, Codex and OpenCode; CodeBurn covers 36 tools across TUI, web, desktop and menubar, adding budget guards and waste analysis.
Full comparison → cc-lensnpx cc-lens: local analytics dashboard over ~/.claude — sessions with replay, cost and cache breakdowns, insights and budgets, team-adoption mode, a yearly Wrapped card. No cloud, no telemetry.
Why switchBoth mine local session files, opposite depth-vs-breadth bets: cc-lens is Claude-only forensics — replay, cache and cost breakdowns over ~/.claude; CodeBurn is the cross-tool ledger unifying 36 tools into one spend view.
Full comparison →