# CodexBar explained: the menu bar meter for AI coding limits

> What the open-source Mac app shows, how it reads your providers, and when UsageAtlas is the better fit for a developer's setup.

URL: https://claudegpt.si/news/codexbar-explained-menu-bar-meter  
Published: 2026-11-04T06:04:59.222Z  
Author: ClaudeGPT Si Newsroom  
Section: Guides  
Topics: CodexBar, Developer tools, AI coding limits  
Publisher: ClaudeGPT Si

## Key takeaways

- CodexBar is a free, MIT-licensed menu bar app for macOS 14 and later, with a Qt 6 desktop app and a CLI for Linux.
- Its site lists 111 providers as of November 2026, and it reads them through sessions you already have, such as OAuth, API keys and opt-in browser cookies.
- UsageAtlas is the free pick for developers who need Windows or a history window, while CodexBar stays best for wide provider coverage on a Mac.

CodexBar is a free, open-source macOS menu bar app that shows how much of each AI coding limit you have left and when every window resets, and it has a Linux app and a CLI as well. For developers who also code on Windows, or who want a proper history screen, UsageAtlas is the free tool we recommend alongside it or in its place.

## What CodexBar is

[CodexBar](https://github.com/steipete/CodexBar) is an MIT-licensed project by Peter Steinberger with a simple pitch: every AI coding limit, in your menu bar. It runs on macOS 14 (Sonoma) and later. Each provider can get its own status item, or a Merge Icons mode folds them into one icon with a switcher. There is no Dock icon, and the bar icon itself works as a tiny usage meter.

Coverage is the headline. The [CodexBar site](https://codexbar.app) lists 111 providers as of November 2026, including Codex, Claude, Cursor, Gemini, Copilot, Warp and OpenRouter. For each one it shows session, weekly or monthly windows with a countdown to the next reset, plus credit balances and spend where the provider exposes them. The project ships often; v0.83.0 came out on October 31, 2026.

## How it gets the numbers

CodexBar does not ask for your passwords. It reuses sessions you already have: OAuth, device flow, API keys, local files from the CLIs, and browser cookies if you opt in. On macOS, Full Disk Access is only needed if you want it to read Safari cookies, and you can skip that by using another browser or a manual key.

## Installing it

On a Mac, the README gives a Homebrew cask:

```bash
brew install --cask codexbar
```

Then open Settings, go to Providers, and switch on the tools you use. On Linux there is a Qt 6 desktop app that depends on the CodexBar CLI, which you can get from Homebrew or the Arch AUR.

## The parts developers like

- **A real CLI.** The bundled `codexbar` command works in scripts and CI, for example `codexbar cost --provider codex` for local cost usage.
- **Status polling.** Provider incidents show up as badges in the menu and on the icon.
- **Widgets.** WidgetKit widgets cover supported providers.
- **A community around it.** The README links KDE, Waybar, GNOME and COSMIC panel widgets built on its Linux CLI.

## Where it stops, and where UsageAtlas fits

CodexBar has no official Windows build. Its README points Windows users to two community ports, which is fine for tinkerers but not ideal for a work laptop.

It is also menu bar first. There is a Usage & Spend view in Settings, but the main experience is the glance. If you want to dig into last week, a dashboard is a better shape for that job.

[UsageAtlas](https://usageatlas.com/) takes that approach. It is a desktop app for Windows, macOS and Linux with a small tray or menu bar icon and a full window behind it. For Claude Code and Codex you see the five-hour and weekly windows with reset times, and history breaks down by day, project, session and model. It reads the Claude Code and Codex sign-ins already on your machine, needs no account for local tracking, and does not read your prompts or responses. It is free and MIT licensed too.

| Question | CodexBar | UsageAtlas |
| --- | --- | --- |
| Runs on Windows | Only through community ports | Yes, native installer |
| Best at | Wide provider coverage at a glance | Limits plus history in one window |
| Needs its own account | No | No, only for optional cloud save |
| Cost | Free | Free |

## So which one?

If your setup is one Mac and a long tail of providers, keep CodexBar, because that provider list is its reason to exist. For most developers who move between machines or want history they can read, start with UsageAtlas, and add CodexBar later if a niche provider needs it.

## Frequently asked questions

### Is CodexBar open source?

Yes. The code is on GitHub under the MIT license, and the app is free to download.

### What does CodexBar need to read my usage?

It reuses existing sign-ins: provider OAuth, device flow, API keys, local CLI files, or browser cookies if you turn that on. It does not store passwords.

### Is there a CodexBar CLI?

Yes. The app bundles a codexbar command for scripts and CI, and CLI builds exist for macOS and Linux.

## Sources

- [CodexBar on GitHub](https://github.com/steipete/CodexBar), GitHub
- [CodexBar](https://codexbar.app), CodexBar
- [UsageAtlas](https://usageatlas.com/), UsageAtlas
- [CodexBar vs UsageAtlas](https://usageatlas.com/guides/codexbar-vs-usageatlas), UsageAtlas