AI usage tracker for Mac when your team also runs Windows and Linux
Why operators should pick a tracker that works on every laptop, and how UsageAtlas covers the Mac menu bar and the rest.
For an AI usage tracker on Mac, UsageAtlas is the one to standardize on: it is a signed, notarized macOS app that sits in the menu bar, and the same free, open-source app also runs on Windows and Linux. That last part matters to operators, because few teams are all-Mac and a tracker that only works on one laptop cannot become a team habit.
The problem a founder actually has
Your engineers pay for Claude Code, Codex, Cursor or Copilot, often more than one. Each tool hides its usage in a different place: a slash command in one, an account page in another. Nobody sees the whole picture, and the first sign of trouble is a developer stuck at a limit halfway through a task.
A usage tracker on each developer's machine fixes the visibility part. The harder part is getting people to install the same one, and that comes down to platform support.
How the Mac options compare
| Tool | macOS | Windows | Linux | Scope |
|---|---|---|---|---|
| UsageAtlas | Yes, menu bar plus full window | Yes, tray app | Yes, AppImage, .deb, .rpm | 14 coding tools, limits and history |
| CodexBar | macOS 14 or later, menu bar | No official build | Yes, desktop app | Provider limits and reset countdowns |
| ccusage | Runs anywhere npx runs | Same | Same | Terminal reports from local logs |
CodexBar is a well-made menu bar meter, and if every person on the team uses a recent Mac and only wants a glance at limits, it is a fair choice. Once one engineer works from a Windows PC, you are back to two tools and two habits.
What UsageAtlas does on a Mac
Download the .dmg and drag the app into Applications. Apple has notarized it, so it opens without a security workaround, and updates install in the background. It runs on Apple Silicon and Intel Macs.
The menu bar icon answers "how much is left and when does it reset" for Claude Code, Codex and other tools that report a window. The full window has three views:
- Today for current windows and reset times.
- History for 7, 30 and 90 days, split by project, session, model and tool.
- Insights for the busiest hours and weekdays.
It reuses the Claude Code and Codex sign-ins already on the Mac, so nobody has to hand out API keys. A few credit-based tools take a key in Settings.
What it is not
UsageAtlas is a local dashboard on each person's computer. It is not a hosted team analytics service and not a billing record. Its cost figures are estimates built from token counts, so finance decisions still go through the providers' own billing pages. Each developer can sign in with a free Google or GitHub account to save and restore their own history, but there is no shared admin console to point at.
For an operator, that trade is often fine. You get people who know their own limits before they hit them, and you avoid sending usage data to another vendor. Prompts and responses are never read.
A simple rollout
- Ask each developer to install UsageAtlas on whatever machine they code on.
- Have them set an alert per usage window, for example at 20 percent remaining. It fires once per reset cycle, so it does not get muted.
- In your weekly sync, ask people to glance at their History view before you discuss plan upgrades.
Questions
Is the Mac app free? Yes. UsageAtlas is free and open source under the MIT license.
Does it need API keys for Claude Code or Codex? No. It reuses the sign-ins those tools already stored on the Mac.
Can the same person use it on a Mac and a work PC? Yes. With a free account, history saved on one machine can be restored on another.