I Built Codex Pulse: A Native macOS Dashboard for Codex and Claude Quotas

Roman Sharafutdinov — Sat, 15 Aug 2026 00:28:19 +0000

If you use Codex and Claude side by side, you have probably done the same tiny ritual many times: open one Usage screen, open another, remember which percentage belongs to which window, and guess whether the remaining quota will last until the reset.

I built Codex Pulse to remove that ritual.

Codex Pulse is an open-source native macOS app that puts Codex and optional Claude Web quota windows in the menu bar, a desktop widget, and one dashboard. It is a public preview for macOS 13+ on Apple Silicon and Intel.

The problem is not a single percentage

“60% remaining” sounds useful, but it is incomplete. To make a sensible decision before starting a long task, I need three different signals:

how much quota remains;
when that particular window resets;
whether my current pace is likely to exhaust it before the reset.

The hard part is that Codex and Claude have different windows and different interfaces. Mixing their data into one “budget” creates another problem: a warning can look as if it belongs to the wrong provider.

What Pulse shows

For Codex, Pulse keeps the weekly Codex window and the separate Codex Spark window visible, including reset time and a pace forecast.

When the source provides usage aggregates, the full dashboard also shows local analytics such as tokens, cache, output, models, projects, days, and an estimated cost.

Claude Web is an opt-in connection through Chrome. Pulse can show the current session, the weekly all-model window, and separate model windows such as Fable when Claude’s Usage page returns them.

The compact widget defaults to Codex, but you can switch between Codex and Claude without opening settings. Each provider keeps its own reset time and pace signal.

Data boundaries are a feature

This is deliberately a read-only, local-first tool.

Pulse does not read chat history or prompt text. It does not store passwords, cookies, API keys, access tokens, or account email addresses. Claude authentication remains in Chrome; the local connector sends only cleaned quota-window data such as labels, percentages, and reset times.

There is one important limitation: Claude Web exposes quota percentages and reset times, not a complete token ledger, project breakdown, or exact spend. Pulse does not invent those missing numbers.

Current limitations

Codex Pulse is a public preview. It is not yet signed with an Apple Developer ID or notarized, so macOS may show its standard one-time warning for an unsigned app.

Claude Desktop without Claude Web is not a direct integration yet. The current Claude view needs an authorized claude.ai tab in Chrome.

Try it

The source code, releases, universal DMG/ZIP downloads, and SHA-256 checksums are on GitHub:

https://github.com/shromarketing/codex-pulse

I would especially value feedback on two things:

Which quota windows do you actually need every day?
At what point does it become unclear whether a limit, reset time, or warning belongs to Codex or Claude?