OpenLimiter 1.2.0
Every bar the providers publish, including Claude's weekly pool for each model. Your quota on your phone, paired by scanning a code the desktop shows. And Pro, which sells alerts, history, phone access, extra accounts and spend tracking above the free ceiling.
The question this product exists to answer has not changed since the first release. You hold several AI coding subscriptions, you have already paid for all of them, and what you actually need to know at four in the afternoon is which of those windows still has room in it. What changed in 1.2.0 is how many places you can ask, and how much of the answer arrives without you doing anything.
Every bar, including one for each model
Nine connectors ship, and the dashboard now draws every window each of them reports rather than the one it happened to know about. That matters most for Claude, which states a separate weekly pool for each model. The reading order puts the session first, then the day, then the week, then the weekly pool for each model, then the month, then credits, so a screen full of bars reads top to bottom in the order somebody actually checks.
A model this build has never heard of is not a problem to be worked around. A code like SEVEN_DAY_OPUS is drawn as Weekly (Opus) without anything in the codebase knowing what Opus is, so a provider that names a new model tomorrow gets a labelled bar today.
- A percentage, on a continuous bar rather than a stepped one, so ninety one and ninety seven do not draw identically.
- An amount with the currency the provider stated, for the plans that are money rather than a percentage.
- A balance, which stays a balance: available, voucher and cash are three separate figures, and none of them becomes a monthly total or a forecast.
- The reset window in the words a person would use, two units at most, so it can be planned around instead of watched.
- A hatched track when a reading is too old to trust. Stale is never painted as a colour band, because a colour says the number is current and a hatch says it is not.
Your quota on your phone, without an application
Open the desktop application, choose to pair a phone, and it shows a QR code that lives for two minutes. Scan it, the phone claims the code, the desktop asks whether to trust the device by name, and you approve it there. Nothing is installed and nothing is in a store.
The code travels in the fragment of the URL, which is the part a browser never sends to a server, so it cannot appear in an access log or a referrer on its way to the phone. The phone prints the same eight characters as text under the instruction, so you can check them against the desktop before you approve anything.
POST /functions/v1/pro-service
x-openlimiter-entitlement: <read scoped device token>
{"action":"read_snapshots"}That token is read only and it is the only thing the phone has. There is no account session on it, it can never change the account or upload anything, and revoking the device from the desktop or from your account page ends its access on the next read. When that happens the phone says so in one sentence rather than showing an empty screen.
What Pro is, and where the line moved
The first release promised that no local feature would ever be withheld to create a paid tier. That promise is stated more precisely now, because two of the six Pro features are switches in the local application rather than servers, and pretending otherwise would be the comfortable sentence rather than the true one.
Everything you can see is free. Alerts, history, phone access, extra accounts and spend tracking above one hundred dollars are Pro.
- Every alert. A desktop notification, an email and a phone push, at sixty, eighty and ninety percent of a window and again when that window resets. Those four moments are the product rather than a setting, and a push payload never carries usage detail, so a locked screen never shows one.
- Ninety days of hosted history, with a forecast to the day a window runs out. A gap stays a gap and is never interpolated.
- Hosted routing context, signed by the service and verified by the release build before an agent reads it. A build without the pinned verification keys injects nothing rather than trusting an envelope it cannot check.
- API spend meters, in a labelled beta. The free plan tracks up to one hundred dollars a calendar month for each source and Pro goes above it.
- More than one account per provider, unlocked in the local application. The free plan allows one active account per provider.
- One Pro accent or density preset, applied in the local application.
Pro is five dollars a month or fifty dollars a year, the first thirty days are free with no card, and a full refund is available on request within fourteen days of any charge. Signing in is separate and free: it exists so your own percentages reach your own other devices, which is why sync is on from the moment you arrive.
Where to start
The same place as always. Install the published package, run the demo against its bundled fixtures, and look at what comes out before pointing it at anything real. The demo touches no cache and no network.
npm install -g openlimiter
openlimiter demoDesktop builds for Windows, macOS and Linux are attached to the release. Windows and macOS are unsigned and each states its one time allow step in full, and macOS is now one universal disk image that runs on Apple silicon and on Intel rather than two files that were never there. If a connector breaks for you, or a number looks wrong, open an issue: a quota tool that guesses is worse than no quota tool at all.