CodexBar Lite

Name: CodexBar Lite
Rating: 4.0 (1 reviews)

Privacy-first Codex tracker for your macOS menu bar

4.0•1 review•

101 followers

Privacy-first Codex tracker for your macOS menu bar

4.0•1 review•

101 followers

•

•

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.

Free

Launch tags:Privacy•Developer Tools•GitHub

Launch Team / Built With

LightfieldAI-native CRM that builds itself and does work for you

Promoted

CodexBar Lite

Maker

📌

Hey everyone! 👋 CodexBar Lite started as a tool I built for myself. I wanted a simple way to keep an eye on my Codex usage while working, but even getting one tracker set up felt like more effort than it should. Most solutions I tried wanted access to Chrome, browser cookies, Keychain, or other permissions just to show usage. So I built one around a simple idea: use the existing codex login session that's already on my Mac. I've been using it daily for the past few months, gradually polishing it instead of launching it. Every time I thought it was ready, I'd find one more thing to improve. Today I'm finally sharing it. A few highlights: - Native macOS app - Uses your existing Codex CLI login - Minimal by design - no Chrome, browser cookies, or Keychain access - No telemetry - Lightweight and open source I'd love to hear what you think. If you use Codex regularly, what would make a menu bar companion genuinely useful for your workflow?

Report

2mo ago

Reusing the existing Codex CLI session instead of asking for Chrome access, browser cookies, or Keychain permissions is exactly the right call for a tool this narrow in scope, most usage trackers overreach on permissions relative to what they actually need to show a number. Months of daily personal use before shipping usually shows in the polish, and it reads that way here. Since it only reads the CLI session, does it break or silently go stale if OpenAI changes how that session is stored, or is there some fallback check built in for that.

Report

2mo ago

CodexBar Lite

Maker

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.

Report

2mo ago

Dial

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?

Report

1mo ago

CodexBar Lite

Maker

@galdayan That's a great question.

The app doesn't read usage from a local cache. It periodically makes the same authenticated request that you'd make yourself to check your usage, using your existing codex login session. It isn't creating a separate account or using a different authentication mechanism.

From OpenAI's perspective, it's just another authenticated request from your existing session, similar to if you checked your usage manually every few minutes. I also keep the refresh interval conservative to avoid unnecessary requests, and one could configure this interval as well.

Report

1mo ago

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?

Report

1mo ago

CodexBar Lite

Maker

@noctis06 That’s a really good question. Right now, the session model is intentionally Codex-specific because the app is built around Codex’s existing CLI authentication and usage data.

The architecture could support other providers, but I’d be careful about turning CodexBar Lite into a multi-provider dashboard, since that would go against the minimal focus.

My current thinking is that another provider would either be a separate lightweight companion app, or an optional integration that stays completely out of the way unless enabled.

The productivity comparison angle is interesting though. Tracking which tool was used for what would require much deeper session-level data than CodexBar Lite currently collects, and I’d want to approach that very carefully from a privacy perspective.

Report

1mo ago

Dial

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

Report

1mo ago

CodexBar Lite

Maker

@omri_ben_shoham1 That's a fair concern. The app uses Sparkle for updates, so update payloads are cryptographically signed and verified before they're installed. If the signature verification fails, the update is rejected. The app is also code signed, so it isn't just a download-and-replace flow.

Report

1mo ago

@wei_b0 - This looks amazing, any plans to build a similar app for Claude and other AI Platforms?

Report

1mo ago

CodexBar Lite

Maker

@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.

Report

1mo ago

@wei_b0 yeah I totally understand but for users like myself who don’t use OpenAI and mainly use Claude code and Kimi Code. Maybe you could look at building different apps for different tooling, although that may not work for users who say use both Codex and Claude Code. They may not want to install two apps.

Report

1mo ago

CodexBar Lite

Maker

@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.

Report

1mo ago

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:)

Report

2mo ago

CodexBar Lite

Maker

@mohammed_messeguem appreciated!

Report

1mo ago

Forum Threads

p/codexbar-lite

•

20d ago

The redesigned CodexBar Lite is now live ✨

A little while ago, I posted here asking what you'd look for first in a redesigned CodexBar Lite.

The feedback was incredibly useful - especially around glanceability, keeping the app lightweight, and making sure a menu bar utility stays out of your way.

After using the redesign myself for a while and polishing the little things, it's now live.

The goal hasn't changed: keep CodexBar Lite minimal, privacy-first, and focused on doing one thing well.

p/codexbar-lite

•

1mo ago

I'm sitting on a redesigned CodexBar Lite... what would you look for first?

I've just finished a pretty substantial UI refresh for CodexBar Lite and I'm using it myself before shipping it.

The functionality is largely the same. The focus this time wasn't adding features, it was making the app feel more polished while staying true to its original philosophy:

Minimal
Privacy-first
Native macOS

Before I hit release, I'm curious: If you were testing a menu bar app, what's the first thing you'd notice or judge?

p/codexbar-lite

•

1mo ago

Thank you ❤️

What a week!

CodexBar Lite closed at #13 Product of the Day with 97 points.
For a first Product Hunt launch, I honestly couldn't have asked for more.

I want to thank everyone who supported the launch, whether you upvoted, commented, tried the app, shared feedback, or simply stopped by to take a look. Every interaction meant a lot.

The launch may be over, but the project certainly isn't.

View all

@noctis06 That’s a really good question. Right now, the session model is intentionally Codex-specific because the app is built around Codex’s existing CLI authentication and usage data.

The architecture could support other providers, but I’d be careful about turning CodexBar Lite into a multi-provider dashboard, since that would go against the minimal focus.

My current thinking is that another provider would either be a separate lightweight companion app, or an optional integration that stays completely out of the way unless enabled.

CodexBar Lite

Privacy-first Codex tracker for your macOS menu bar

Privacy-first Codex tracker for your macOS menu bar

Forum Threads

The redesigned CodexBar Lite is now live ✨

I'm sitting on a redesigned CodexBar Lite... what would you look for first?

Thank you ❤️

Forum Threads

The redesigned CodexBar Lite is now live ✨

I'm sitting on a redesigned CodexBar Lite... what would you look for first?

Thank you ❤️

What's great

What needs improvement

What's great

What needs improvement