Lumo

Lumo

  A local-first desktop overview for tracking Claude Code usage.
  Cost, tokens, sessions, and active coding time, all from your own machine.

  中文文档

  Why •
  Features •
  How It Works •
  Install •
  Develop •
  macOS Troubleshooting •
  Tech Stack

Why Lumo?

Claude Code provides powerful assistance, but its usage is difficult to observe in aggregate.

Typical questions are hard to answer:

- How much did I actually spend today or this week?
- Which models or sessions consume most of the cost?
- How long am I actively coding with Claude?
- Am I using caching effectively?
- Do I have long, uninterrupted coding sessions without breaks?

Lumo exists to answer these questions locally, using the data Claude Code already emits.

No accounts.
No cloud dashboards.
No data leaving your machine.

What Lumo Does

Lumo runs a local daemon and desktop app to collect Claude Code telemetry and present it as dashboards.
It stores data in a local SQLite database and renders a native desktop UI (Tauri + Next.js).

The goal is not to analyze your code or conversations,
but to provide clear visibility into usage patterns, cost, and time.

Lumo is built for developers who want to understand:

- where Claude Code time and spend go every day
- which sessions/models are driving most usage
- whether work patterns are sustainable (long streaks, break timing, etc.)

On first launch, Lumo also attempts to configure Claude Code locally so telemetry and hook events are forwarded to the Lumo daemon automatically.

Screenshots

Lumo provides a desktop dashboard for understanding Claude Code usage at a glance:
cost trends, token breakdown, session counts, code changes, and activity heatmaps.

Features

Overview

An at-a-glance overview of your Claude Code…