explaingit

ewijaya/lmtop

Analysis updated 2026-05-18

3RustAudience · developerComplexity · 2/5Setup · easy

TLDR

A terminal dashboard, like top for AI coding subscriptions, that tracks quota usage, burn rate, and reset times for tools like Codex and Claude Code.

Mindmap

mindmap
  root((lmtop))
    What it does
      Quota monitoring
      Burn rate tracking
      Reset countdowns
    Tech stack
      Rust
      Ratatui
      Terminal UI
    Use cases
      Subscription capacity planning
      Status bar embedding
      Multi provider tracking
    Audience
      Developers
      AI coding agent users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Track how much subscription quota remains for Codex or Claude Code before it resets.

USE CASE 2

See how fast you are burning through a flat-rate AI coding subscription's quota.

USE CASE 3

Embed a one-line usage summary into a tmux or terminal status bar.

USE CASE 4

Compare local observed token usage against the provider's official quota percentages.

What is it built with?

RustRatatui

How does it compare?

ewijaya/lmtopadsharma/ast-grepcodeitlikemiley/antigravity-sdk-rust
Stars333
LanguageRustRustRust
Setup difficultyeasyeasyhard
Complexity2/53/54/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Requires an existing OpenAI Codex or Claude Code CLI installation with local usage data for lmtop to read.

In plain English

lmtop is a terminal dashboard tool, similar in spirit to the classic Unix tool top, but built specifically for tracking how much of your AI coding subscription capacity you have used up. It is aimed at people on flat-rate subscription plans for tools like OpenAI's Codex or Claude Code, rather than people paying per API call, and answers a specific question those tools do not: how much of my quota is left, when does it reset, how fast am I burning through it, and am I likely to run out before the reset happens. The tool keeps three kinds of information strictly separate: locally observed token usage read from your own agent session files, the official quota percentages reported directly by the provider, and a note that estimated dollar cost is intentionally not calculated, since flat-rate plans apply hidden weighting that makes a real cost estimate misleading. On top of the provider's reported quota trend, it calculates how fast that quota is being consumed per hour and projects whether the current quota window will last until its reset time or run out first. It supports both OpenAI Codex and Claude Code, showing local token usage, active sessions, weekly usage broken down by model, and reset countdown timers for each. A live mode can optionally check the same usage endpoints the providers' own official tools use, using the access token those tools already store locally, while an offline mode ensures no network requests happen at all. Installation options include Homebrew on macOS and Linux, an apt repository for Debian and Ubuntu, downloading a pre-built binary for your platform, or building it from source using Rust's cargo tool. Once installed, it can run as a full interactive dashboard, print a one-shot text or JSON summary, or output a single line suitable for embedding in a terminal status bar like tmux.

Copy-paste prompts

Prompt 1
Help me install lmtop using Homebrew and run the combined dashboard.
Prompt 2
Explain the difference between observed tokens and provider quota that lmtop tracks separately.
Prompt 3
Show me how to set up lmtop line in my tmux status bar.
Prompt 4
Walk me through enabling live quota mode with lmtop and what data it sends over the network.

Frequently asked questions

What is lmtop?

A terminal dashboard, like top for AI coding subscriptions, that tracks quota usage, burn rate, and reset times for tools like Codex and Claude Code.

What language is lmtop written in?

Mainly Rust. The stack also includes Rust, Ratatui.

How hard is lmtop to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is lmtop for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.