OPEN-SOURCE PRODUCT · MACOS MENU BAR APPSystems online

Your AI quotas in the menu bar, before you hit the wall.

A native macOS menu bar app that keeps every AI subscription quota visible — Claude Code, Codex, SuperGrok, Cursor, OpenRouter, MiniMax, OpenCode and MiMo. One colored strip in the menu bar, one popover with the full picture, and a notification before you run out instead of after. All local, open-source under MIT.

MIT · macOS 13+ · Swift 5.9 · 8 providers · 180 testes

§01·Why

Subscription AI tools don't warn you

Claude Code's 5-hour window closes mid-refactor, the weekly cap lands on a Thursday, and the first sign of trouble is a "you've reached your limit" message. Meanwhile the quota you do have sitting on another subscription goes unused, because nothing tells you it's there.

OkTally keeps every one of those quotas visible at a glance: a glyph per provider in its identity color, the remaining percentage colored by how close it is to the limit, and a macOS alert the moment a threshold is crossed — once per crossing, not once per poll.

It is Okami Tally's Mac sibling: the same mission as the iPhone app, now as an open-source menu bar app — running where the coding sessions actually happen.

§02·Features

What OkTally does

PIN

Colored menu bar, as many pins as you want

Pin any number of quota windows. Each renders as a provider glyph in its identity color with the remaining percentage — green above 30%, amber at or below 30%, red at or below 10%. Pin nothing and the app automatically shows whichever window is closest to its limit.

08

Eight providers, one protocol

Claude Code (with one-click import of your existing CLI login), Codex, SuperGrok, Cursor, OpenRouter, MiniMax, OpenCode and MiMo. Each provider is a plugin behind a single protocol that normalizes everything into one quota model — rolling window, periodic counter, credit balance, metered or estimated.

POP

A popover that answers the question first

A hero gauge spotlights the window closest to running out, with a countdown to its reset. Below, per-provider cards with a ring gauge and one row per window. Providers that errored or aren't configured collapse into quiet rows at the bottom.

ALRT

Notifications before the wall

An edge-triggered alert engine fires a macOS notification the moment a threshold is crossed — once per crossing, not once per poll. You switch providers before burning the session, not after.

PREF

Preferences that feel like System Settings

A sidebar lists every provider with a live status dot, one pane per provider — OAuth, API key or web session — plus a General pane for reordering and removing menu bar pins.

LOC

Everything local: Keychain and SQLite

OAuth tokens and API keys live in the macOS Keychain, never in plaintext. Usage history sits in a local SQLite database. No telemetry, no analytics, no external server — the app talks only to the providers' own APIs.

§03·Specs

OkTally specs

PlatformmacOS 13+
StackSwift 5.9 · SwiftUI · SQLite
ProvidersClaude Code, Codex, SuperGrok, Cursor, OpenRouter, MiniMax, OpenCode, MiMo
AuthenticationOAuth · API key · sessão web · import da CLI
DataKeychain do macOS · SQLite local
Backend
Tests180 unit tests
LicenseMIT
DistributionDMG (GitHub Releases) · build from source
§04·Use cases

When to use OkTally

01

Long subscription-backed coding sessions

A glance at the menu bar tells you whether the 5-hour window can take the refactor — and the alert arrives before the session dies mid-run, not after.

02

Anyone rotating across several subscriptions

Claude for code, Codex for review, Cursor in the editor, OpenRouter for the rest. The colored pins show where you still have headroom without opening a single web dashboard.

03

Anyone who keeps credentials on-device

Tokens and keys stay in the macOS Keychain, history in a local SQLite database, and queries go straight from the Mac to each provider. There is no intermediary server — not Okami's, not anyone's.

§05·FAQ

OkTally FAQ

What's the difference between OkTally and Okami Tally?+

Same mission, different platforms. Okami Tally is the closed-source iPhone app, distributed through the App Store, with widgets and the Dynamic Island. OkTally is the open-source (MIT) macOS menu bar app, distributed via GitHub Releases — built for the Mac where the coding sessions happen.

How do I install OkTally?+

Download the DMG from the GitHub Releases page and drag it to Applications. The app is not notarized: on first launch, right-click OkTally.app → Open → Open. You can also build from source with Swift 5.9+ (bash Scripts/build_app.sh) and install a launch agent to start at login.

Do I have to log in to every provider again?+

Not always. Claude Code imports your existing CLI login in one click, and Cursor is automatic — the app reads your local Cursor session. The others use OAuth, an API key or, for MiMo, an in-app web session that recovers on its own when the cookie expires.

Does my usage data leave the Mac?+

No. OAuth tokens and API keys live in the macOS Keychain, usage history in a local SQLite database, and the app talks only to the providers' own APIs. There is no telemetry, no analytics and no external server.

Want OkTally running in your context?

The product is open and you can run it yourself. Rolling it out in your environment, with integration and a documented hand-off, is the consulting.