v0.1.0

tokenleader v0.1.0 — first public release

Self-hosted token-usage leaderboard for Claude Code, Codex CLI, and Cursor. It reports token counts, model names, and timestamps — never message content.

Highlights

• Server: Bun + Hono + bun:sqlite (single-file, WAL). Typed env configuration with zero required variables (src/server/config.ts owns the full contract, mirrored in .env.example and enforced by a parity test).
• macOS daemon (Apple Silicon + Intel) that parses local Claude Code / Codex CLI session logs and posts token counts, with sha256-verified, atomically-swapped auto-update.
• One-command install served by each team's own server (/install), with a matching /uninstall.
• Dashboard: React SPA (Vite + TanStack Router/Query) served by the same container; optional viewer token (TOKENLEADER_DASHBOARD_TOKEN) with a cookie-based /login.
• Stable API: GET /api/v1/usage with uniform half-open UTC ranges [since, until) (unix-ms or strict ISO-8601 input), optional bearer auth.
• Identity: per-user TOFU ingest identity, plus an optional join code (TOKENLEADER_JOIN_TOKEN) gating first claims of new leaderboard names.
• Cursor mirror (optional): server-side usage import via the Cursor Teams Admin API (off by default; requires an explicit email-to-handle map).
• Binary mirror: the server caches daemon binaries and manifest.json locally so teammate machines never call GitHub.
• Deploy targets: Dockerfile + docker-compose (ghcr.io image), Railway template, fly.toml; Litestream backup profile.
• Tag-driven release pipeline: one vX.Y.Z tag builds the daemons, emits the dual-shape manifest, publishes release assets, and pushes the multi-arch server image.