Notchlet vs ccusage
ccusage generates detailed terminal reports from coding-agent logs. Notchlet reads provider usage limits and shows them alongside history in your Mac's notch.
Feature comparison
Checked Sep 13, 2026.
| Notchlet | ccusage | |
|---|---|---|
| Lives in | The notch, expanding on hover. | Terminal, with a Claude Code status-line integration. |
| Tracks | Claude Code, Codex, Cursor and OpenCode, three at a time. | Claude Code, Codex, OpenCode and other agent CLIs. |
| Reads | Saved provider logins or pasted credentials, then provider usage APIs. | Local usage logs. Offline mode uses cached pricing data. |
| History and cost | Token counts, estimated API cost, a yearly activity graph and per-model usage from local logs and provider records. | Daily, weekly, monthly, session and five-hour block reports, with model breakdowns. |
| Share | A PNG of your numbers, graph and models. | JSON export and compact tables for screenshots. |
| Price | Free. | Free. |
| Source | MIT on GitHub. | MIT on GitHub. |
| Runs on | macOS 14 or later. | Runs through Node.js or Bun on supported systems. |
ccusage facts from its README.
Choosing a tool
Choose ccusage if
- You want reports you can script or export as JSON.
- You need detailed filters or support for more agent logs.
Choose Notchlet if
- You want remaining limits reported by your provider.
- You prefer a native Mac interface.
- You want a local history archive and PNG sharing.
