Ways to use OpenUsage

OpenUsage is more than the dashboard. The same usage data is available through several surfaces — pick whichever fits how you work. They all read the same providers and (optionally) the same local history.

Surface	Command	Use it when
Live dashboard	openusage	You want the full interactive view
CLI reports	openusage daily (--json)	Scripting, CI, a quick check
Claude Code statusline	openusage statusline --install	You live in Claude Code
tmux status bar	openusage tmux install	You live in tmux
Background daemon	openusage telemetry daemon install	You want history over time
Multiple machines	openusage hub / hub-view	You work across several machines
Export	openusage export --json	You want to pipe data into your own tools

Live terminal dashboard

The default. Auto-detects your tools and shows live tiles with a master/detail panel and an Analytics screen (Tab).

openusage

See first run.

Headless CLI reports

The same parsing and pricing as the dashboard, printed once and exited — handy for scripts, CI, cron, and quick checks. Add --json for machine-readable output.

openusage daily          # also: weekly, monthly
openusage session        # grouped by session
openusage blocks         # by 5-hour billing block, with burn rate + projection
openusage daily --json

See the headless reports & statusline guide.

Claude Code statusline

Put session/today/block cost, burn rate, and context usage right in Claude Code's own status line.

openusage statusline --install

See the reports & statusline guide.

tmux status bar

A one-line provider-usage segment in your tmux status bar, updated on tmux's interval. The interactive installer also offers real provider icons.

openusage tmux install

See the tmux integration guide.

Always-on background daemon

Run a background collector that ingests snapshots into a local SQLite store, so reports and analytics span time even when the app isn't open. Local-first — the daemon listens only on a Unix socket.

openusage telemetry daemon install

See Daemon & Telemetry.

Across multiple machines

Aggregate usage from several machines into one view: run a hub that collects from each, and view the combined picture.

openusage hub          # aggregate snapshots from multiple machines
openusage hub-view     # view a remote hub's aggregated data in the TUI

See the multi-machine guide.

Export & scripting

Emit current usage snapshots to a file or stdout for your own tooling.

openusage export --json

See the CLI reference.