cc-lens vs codeburn
npx 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. — versus — Local-first cost ledger for AI coding: reads the session files 36 tools already write and breaks every token and dollar down by task, model, project. TUI, web, desktop, menubar — no proxy, no keys.
Both 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.
| cc-lens | codeburn | |
|---|---|---|
| Stars | 574 | 9.0k |
| Forks | 77 | 708 |
| Language | TypeScript | TypeScript |
| License | MIT | MIT |
| Last activity | 1 months ago | today |
| Topics | coding | coding, local |
| Curated connections | 4 | 2 |
cc-lens — the curator's take
The zero-friction option among Claude Code dashboards: one npx command, loopback-bound by default, and v0.4's Insights tab actually recommends actions — cache, model choice, compaction, plan-fit and budget opportunities mined from your own usage — instead of just charting it. Team mode (shared-folder push hub + terminal digest) is a real differentiator for leads tracking adoption. Costs are estimates from a local pricing table (`~/.cc-lens/pricing.json` to override) — treat them as directional and keep the table current. Claude-only; for subagent forensics and ticket linking, claude-code-karma digs deeper; for a number next to your clock, ai-token-monitor.
codeburn — the curator's take
The honest architecture for spend tracking — read the session files already on disk, no proxy in your API path, nothing leaves the machine — executed at the broadest scope in the category: 36 tools, four surfaces, one data source. The parts beyond pretty dashboards earn the install: waste detection with applyable (and undoable) fixes, budget guards, model comparison. Limits are inherited from the source: it sees what session logs record, and subscription flat fees vs metered API blur what a 'dollar' means — treat per-task cost as a good estimate, not accounting (pricing via LiteLLM's daily refresh). When NOT: single-tool Claude Code forensics — cc-lens and claude-code-karma go deeper there with replay and cache breakdowns.