Launched this week
CodexBar Lite is a native macOS menu bar app that keeps your OpenAI Codex usage visible at a glance. It uses your existing Codex CLI session - no browser cookies, Keychain permissions, API keys, or third-party accounts required. Monitor usage, reset times, and receive notifications, all from a lightweight, open-source app.
CodexBar Lite
CodexBar Lite
It would silently stop fail if OpenAI changes the session format. That said, I use it every day myself and have been maintaining it for almost 2 months now, so these issues usually get caught quickly.
I’ve also added OTA updates, which makes it easier to ship fixes whenever something changes on OpenAI’s end.
@wei_b0 - This looks amazing, any plans to build a similar app for Claude and other AI Platforms?
CodexBar Lite
@codeandsea Definitely, I'd love to!
The only thing I'd be careful about is preserving the philosophy of the app - keep it minimal, focused, and avoid turning it into another bloated usage dashboard.
CodexBar Lite
@codeandsea Totally understandable. I wonder if there's a nice middle ground where a single app can stay minimal but be configurable enough to support multiple AI platforms. That might solve the problem for both groups of users without sacrificing the original philosophy.
the no-Chrome, no-Keychain, no-API-key approach is a genuinely refreshing default for a tool this small in scope, most usage trackers ask for way more than they need. one thing I'm curious about since it's riding on your existing CLI session - does the polling itself count against anything on OpenAI's side, like a second process making periodic calls with your session credentials showing up as unusual activity, or is it reading something more like a local cache rather than actually hitting their API each refresh?
Privacy-first design makes sense for a dev tool — anything touching an active coding session should be careful about what it asks for. The no-Keychain, no-browser-cookie approach is reassuring. I use a mix of AI coding tools across projects and the comparison question comes up constantly: when you are running both Codex and something like Claude Code in the same workflow, there is no easy way to see which got used for what and track where the actual productivity gain is. Is the session model specific enough to Codex that adding a second provider would need a separate app, or is the architecture flexible enough to slot in another CLI session alongside the Codex one?
the no-Chrome no-Keychain angle is nice but the OTA auto-update piece is the part that'd actually worry me a little - an app that's already got a live coding session in view and can push its own updates is a decent supply chain target if the update channel or signing ever got compromised. is there any code signing/checksum verification on the update payload before it installs, or is it more of a basic download-and-replace flow right now
Loving the choice to lean on the existing CLI session instead of asking users to generate yet another API key, lovely detail that makes a tool feel trustworthy:)
CodexBar Lite
@mohammed_messeguem appreciated!