Show and tell: kimi-usage — npx one-liner for a live, local usage dashboard

[coconilu]

I built a zero-dependency usage analytics dashboard for Kimi Code CLI and wanted to share it here — it parses the local wire.jsonl session logs (same data source as ccusage) and answers the question "where did my quota actually go?" with per-day / per-model / per-project / per-session breakdowns.

Quickstart

npx kimi-usage

That's the whole install. It scans your logs (~1s for 800+ sessions), starts a local server, opens the dashboard, tails the logs and pushes new usage to the page in real time (SSE), and exits by itself ~60s after you close the browser tab. No daemon, no config, data never leaves the machine (127.0.0.1 only).

npx kimi-usage --export report.html   # self-contained static HTML, shareable

What's on the page

• KPI cards: weekly total, today, cache hit rate, active sessions, week-over-week (with human-readable 亿/万 units for large numbers)
• Daily token trend (input / output / cacheRead stacked) + today's trend by hour
• Model share (pie + per-day stacked) — handy when you mix k3 / glm-flash / deepseek
• Cache hit-rate by day
• Project ranking (grouped by working directory, from session_index.jsonl)
• GitHub-style yearly activity calendar (day-level, full history regardless of --days)
• Session details table, sortable by start / end / total

Implementation notes

• Single 34KB Node.js file, built-in modules only — no dependencies, ships via npm as kimi-usage
• Only turn-scoped usage.record entries are counted (session-scoped records are cumulative and would double-count)
• Live mode tracks per-file byte offsets on wire.jsonl, so updates are incremental
• A Python fallback (static export only) lives in the same repo for machines without Node

Repo: https://github.com/coconilu/kimi-usage-dashboard · npm: https://www.npmjs.com/package/kimi-usage

Happy to take feedback — especially on what other dimensions people want to see broken down.