Compared
Notchlet vs CodexBar
CodexBar is the wide one. If you pay for six AI subscriptions and want them all in one dropdown, it is the better tool, and it is MIT too. Notchlet tracks four agents and puts them in the notch instead of the menu bar, with a year of history and a share image.
Side by side. Checked Sep 4, 2026.
| Notchlet | CodexBar | |
|---|---|---|
| Lives in | The notch. Nothing until you hover. | The menu bar, with a dynamic bar icon. |
| Tracks | Claude Code, Codex, Cursor and OpenCode, three at a time. | Over 60 providers, from Codex and Claude to OpenRouter and Ollama. |
| Reads | The login each CLI already saved, then the usage endpoint behind /usage or /status. Never browser cookies. | Provider config files, local JSONL logs, and browser cookies or local storage for the providers that need them. |
| History and cost | Cost and tokens for today, 7 and 30 days, a 12 month activity graph and per-model tokens, from the logs on your Mac. | Local 7 and 30 day spend estimates, plus credit balances and billing dashboards where a provider has them. |
| Share | A PNG of your numbers, graph and models. | None listed. |
| Price | Free. | Free. |
| Source | MIT on GitHub. | MIT on GitHub. |
| Runs on | macOS 14 or later. | macOS 14 or later. A CLI build also runs on Linux. |
CodexBar facts from its README. If one is wrong, open an issue and it gets fixed.
Which one. Pick by what you run.
CodexBar if
- You use providers beyond Claude Code, Codex, Cursor and OpenCode.
- You want it in the menu bar, not the notch.
- You want credit balances and billing dashboards in one place.
Notchlet if
- You run one to three coding agents and want the menu bar left alone.
- You want a year of usage history and a PNG to share.
- You do not want an app reading browser cookies. Notchlet never does.