Skip to content
OpenLimiter Pro is here. Desktop alerts, account access and local meters are free. Pro adds history, phone push and email alerts, extra accounts and cloud API spend metering.
Account

Track usage across all your LLMs. Real time. Desktop, mobile, and terminal.

Read your AI subscription quota locally. Give agents bounded budget state and advice. Open source, local first, cross platform.

Open the web appInstall on iPhoneInstall on Android

Usage, tools and settings in one window

The desktop has three tabs: Usage for the bars, Connect Tools for provider setup and Settings for the choices around the app. The hover panel keeps limits and agents close when the window is away.

The OpenLimiter desktop Usage tab window with synthetic bars for Codex, Claude Code and OpenRouter.

The real Usage tab window rendered headlessly with synthetic fixtures. No personal account, credential or real usage figure appears in it.

Demo data

Keep working. See when an agent needs you.

The edge tab and terminal show local readings. Pair your phone from the desktop to see its bars on the home screen.

What it reads, where it lands

No testimonials, no avatar wall, no user count. Every card below either ships a connector in this release or says plainly that it does not have one yet, so the wall itself is a status report. Connecting a provider normally happens in the desktop application; the surfaces below are the developer paths, under Advanced, for anyone who wants them directly.

Claude

Parses the rate limit block Claude Code already hands to your statusline command. It asks nothing of Anthropic on its own.

OpenRouter

Parses the credits shape OpenRouter documents. The key belongs in your operating system credential store, never in a file.

Codex

Parses the usage shape the Codex tooling produces. The shape is internal, so it can change without notice, and it fails closed when it does.

Antigravity

Parses the quota shape the Antigravity tooling produces. Internal too, marked as such, and never repaired or rewritten.

OpenCode

Reads OpenCode usage through its experimental adapter and clearly marks the version and setup it requires.

Grok Build

Reads the billing windows exposed to the installed Grok session and fails closed when the shape changes.

Gemini CLI

Reads Gemini CLI usage from local session data and reports the provider window when it is available.

Kimi

Reads the usage windows exposed to the installed Kimi session and fails closed when the shape changes.

Claude Code statusline

Reads the provider statusline locally and shows its current quota window without sending credentials.

Claude Code prompt hook

A bounded hook can capture prompt events as untrusted data, with no provider action when the source is unknown.

Any shell

Runs shell commands as the source of truth, with explicit permissions, bounded output, and no hidden network access.

Any tool that can write a file

Writes a local snapshot for your own tools, using explicit paths and no hidden provider request.

Continuous integration

Export the cache as JSON and assert on it in a pipeline. Every release is tested on Windows and Linux on every push.

Your own front end

The cache is a plain document on your disk with a versioned schema. Read it and build whatever view you want.

Works with your tools

One meter over every subscription you already hold. Connect a provider from the desktop application, or use manual entry or ingest under Advanced. Local mode has zero telemetry and no account. Pro sends only selected bounded quota snapshots to the hosted service after you sign in.

Ships today

Eight connectors ship in this release

Claude CodeConnector
OpenAI CodexConnector
Google AntigravityConnector
Gemini CLIConnector
Grok BuildConnector
KimiConnector
OpenCodeConnector
OpenRouterConnector

What each one actually does

A parser is not a connection

  • ClaudeLocal CLI
    Parser
    Ready
    Reader
    Ready
    Auth
    Not required
    Verification
    Unverified

    Claude Code writes a rate limit block to its statusline command.

  • OpenRouterConnected
    Parser
    Ready
    Reader
    Ready
    Auth
    Ready
    Verification
    Unverified

    The credits endpoint is documented and its response parses.

  • CodexLocal CLI
    Parser
    Ready
    Reader
    Ready
    Auth
    Ready
    Verification
    Verified

    An internal payload shape, which can change without notice.

  • AntigravityLocal CLI
    Parser
    Ready
    Reader
    Ready
    Auth
    Not required
    Verification
    Unverified

    An internal payload shape, which can change without notice.

  • OpenCodeConnected
    Parser
    Ready
    Reader
    Ready
    Auth
    Ready
    Verification
    Unverified

    A usage view behind a session you already hold.

  • Gemini CLIConnected
    Parser
    Ready
    Reader
    Ready
    Auth
    Ready
    Verification
    Unverified

    Model quota returned through the installed Gemini CLI session.

  • Grok BuildConnected
    Parser
    Ready
    Reader
    Ready
    Auth
    Ready
    Verification
    Unverified

    Subscription windows returned through the installed Grok session.

  • KimiConnected
    Parser
    Ready
    Reader
    Ready
    Auth
    Ready
    Verification
    Unverified

    Subscription windows returned through the installed Kimi session.

Reader means something in OpenLimiter goes and fetches the number. Auth means a credential is held and used. Every cell above is read at build time from the reviewed provider registry rather than written into this page, so a stage cannot be claimed here without a human changing a spec first. The registry describes 14 further products with no connector at all, which is why they are not rows here. A row on this page is only ever called Connected once a live reader for it is confirmed, never on the strength of a parser alone.

Every connector ships marked UNVERIFIED, the honest default: no verifier has confirmed a shape against a live account yet. Three read interfaces internal to somebody else's tooling, and when one changes, that provider fails closed to unknown rather than guessing. Every connector and its real state.

Product names, logos, brands, and other trademarks featured or referred to within OpenLimiter are the property of their respective trademark holders. These trademark holders are not affiliated with OpenLimiter, our products, or our website. They do not sponsor or endorse OpenLimiter. Use of them does not imply any affiliation with or endorsement by them.

One small tab. Your limits and agents on hover.

OpenLimiter keeps one small tab with its logo on the left edge of your screen, about 70% of the way down. Hover it to open a panel beside it with your limits and your agents. It works the same on Windows, macOS and Linux X11; on Linux Wayland the tray takes its place. Local meters and desktop alerts are free, with one active account per provider.

The real OpenLimiter edge tab, a small tab with the OpenLimiter logo and a yellow dot, on the left edge of a desktop with a mountain lake wallpaper.

The tab rests on the left edge. A small dot appears when something needs a look, like an agent waiting for you.

Demo data
The real OpenLimiter panel open beside the edge tab, with synthetic data: Claude Code needs you and offers Show app, Codex is busy and Gemini CLI is done, then limits for Codex, Claude Code and OpenRouter with bars and reset times, and an Open app link.

Hover it and the panel opens: agents first, with Show app for the one that needs you, then limits, tightest first, with reset times.

Demo data

Three desktop tabs. One hover panel when you step away.

Usage, Connect Tools and Settings keep the desktop clear. The hover panel puts limits and agent activity beside you when the main window is out of reach.

OpenLimiter desktop Usage tab with synthetic bars for Codex, Claude Code and OpenRouter.

Usage shows the bars for Codex, Claude Code and OpenRouter.

Demo data
OpenLimiter desktop Connect Tools tab showing synthetic provider connections.

Connect Tools shows provider setup and connection status.

Demo data
OpenLimiter desktop Settings tab showing choices for the application.

Settings shows the choices that shape the desktop.

Demo data

Your limits beside your prompt.

The terminal status line shows usage, reset times and freshness for supported hosts. Green, yellow, orange and red bands make a filling window easy to spot. Percentages and labels keep the meaning clear without relying on colour.

openlimiter statusline

5h [███░░░░░░░] 37% ·1h12m7d [█████░░░░░] 58% ·2d5hfable7d [██████░░░░] 63% ·4d19hcx7d [████████░░] 82% ·5d8hag5h [█████████░] ~91% ·2h26mor $12.54oa $8.20an $3.10

This is the real CLI renderer with synthetic readings. Status line support depends on the host. See the CLI guide for setup.

Demo data

Pair from the desktop. Your bars on your home screen.

Pair your phone from the desktop, then open the web app from its home screen. It shows the latest readings from your computer, including when they were observed.

The paired OpenLimiter phone app showing every connected provider and its usage bars.

Usage

Demo data
The paired OpenLimiter phone app showing the Pro tab with its trial and paid features.

Pro

Demo data
The OpenLimiter phone app showing the iOS installation sheet in Safari.

Install

Demo data
The OpenLimiter phone app waiting for the desktop to approve pairing with a synthetic code.

Pair

Demo data

The phone follows its light or dark theme and keeps the last readings when it is offline. Your computer still collects new readings, and provider credentials stay on that computer.

Open the phone app

Real application screens with synthetic data. No personal account or usage data.

Both of those are written up in full: what an agent is told and every command it ships with.

FAQ

What actually leaves my machine?
In local mode, nothing leaves for OpenLimiter. Provider connections talk only to that provider through a fixed allowlist, and local credentials stay on your device. When you sign in, selected bounded quota snapshots go to the hosted service so your own devices can see them. Pro adds history, phone push and email alerts, extra accounts and cloud API spend metering. An API key you explicitly enable for cloud metering is stored encrypted for that job and deleted when you turn it off or ask. Desktop alerts are free.
Is it safe to point at my tools?
OpenLimiter opens what your installed tools already store, read only, and never rewrites, repairs or migrates them. Every parser keeps bounded numbers and timestamps and discards provider text before anything reaches your agent.
Can the prompt hook break my session?
No. The hook reads the local cache, makes no network request, injects nothing when every provider is unknown, and exits 0 whatever happens. The statusline behaves the same way: if input is absent or malformed it falls back to the cache and reports unknown.
Which providers work today?
The provider guide lists the available meters, setup steps and verification status for each integration. Quota readings and agent activity are separate capabilities. A provider that reports activity does not necessarily expose a quota, and a parser tested on fixtures is not proof of live acquisition.
Do I need an API key?
Not to start. The Claude path reads a payload Claude Code already hands your statusline, and the manual path needs nothing at all. OpenRouter is the one connector that expects a key of your own, and that key belongs in your operating system credential store.
Does it route my requests for me?
No, and it is not going to. OpenLimiter provides advice. It does not route requests automatically, does not bypass a limit, and does not touch how your agent authenticates. The decision stays with you.
What happens when a connector breaks?
Unofficial shapes change without notice. When one does, parsing fails closed: that provider returns to unknown, the other providers are unaffected, and nothing invents a number to fill the gap. Unknown never becomes zero.
Is there a desktop or phone app?
The desktop tray application ships for Windows, macOS and Linux. Windows and macOS are unsigned, so each asks once: on Windows, SmartScreen, choose More info then Run anyway; on macOS, open System Settings, go to Privacy and Security, and choose Open Anyway. macOS ships as one universal disk image and stays out of automatic updates until signed and notarised builds exist. On a phone, the web app opens in the browser and installs to a home screen, and the desktop application pairs a phone by QR code so it can read your quota. Native iOS and Android applications are not built, nothing is in a store, and there is no waiting list. The download page lists every platform with its real state.
Is it free?
Everything you can see is free and always will be, under Apache 2.0. The OpenLimiter account is free. Desktop alerts are free. Pro adds history, phone push and email alerts, extra accounts and cloud API spend metering. Only usage percentages sync, never local provider credentials.
What is OpenLimiter Pro?
OpenLimiter Pro is $5 a month or $50 a year, with the first 30 days free and no card required. It adds four things: history with a forecast; email and phone push alerts at 60, 80 and 90 percent and on reset; more than one account per provider; and cloud API spend metering for keys you explicitly enable. Desktop alerts, local meters and account access remain free. A full refund is available on request within 14 days of any charge.
Do I get alerts when a window fills up?
Yes. Desktop alerts are free. Pro adds email and phone push alerts at 60, 80 and 90 percent of a window and again when that window resets. Those four moments are the product rather than a setting. A push payload never carries usage detail, so a locked screen never shows one.
Can I see my quota on my phone?
Yes. The desktop application shows a QR code that lives for two minutes, you scan it with the phone, and you approve the pairing back on the desktop. The phone then holds a read only token: it can never change the account or upload anything, and revoking that device from the desktop or from your account page ends its access at once. Phone access does not require Pro.
What does cloud API spend metering include?
Cloud API spend metering is a Pro beta for keys you explicitly enable. It reads the provider's own billing surface, so it needs an organisation admin or management key and a project key will not work. Moonshot is read as a balance rather than as spend, in three separate figures, and is never turned into a monthly total, a forecast or a budget alert.

Pricing

Local meters, desktop alerts and account access are free, with one active account per provider. Pro adds history, phone push and email alerts, extra accounts and cloud API spend metering.

OpenLimiter

available

Freeforever, and in the licence

The local product and the account are free. Sync is on from the moment you sign in, because moving your own percentages between your own devices is what signing in is for.

  • Every supported provider
  • Sync across your own devices, on from your first sign in
  • One active account per provider, and Pro raises that
  • No usage limit and no charge for the account. Everything you can see is free
Open source under Apache 2.0, so this cannot be taken away later. The licence is the promise.

OpenLimiter Pro

available

$5a month

or $50 a year

Four Pro features: history, phone push and email alerts, extra accounts and cloud API spend metering.

  • Email and phone push alerts. Local desktop alerts are free
  • History and forecasts for synced readings
  • Extra accounts per provider
  • Cloud API spend metering from opted in provider keys
  • Ninety days of hosted history, with a forecast

Spend meters need an organisation admin key. Full refund within 14 days, cancel any time in the Stripe portal. Sold by Lucas Costa, payments by Stripe. Full conditions

Start your free 30 day Pro trial

After the trial, local meters, local alerts and free account access keep working. Free keeps one active account per provider.

OpenLimiter is an independent open source project for people who hold several AI coding subscriptions at once and would rather know which one still has room than find out the hard way, mid task.

It is built around three commitments that are easy to state and awkward to keep. If it saves you an afternoon, sponsorship is the best way to keep the connectors working as the shapes underneath them shift. Reporting a connector that broke is worth just as much.

It runs on your machine

Local mode has zero telemetry. The account is free. Provider connections talk only to that provider through a fixed allowlist, with credentials held by the operating system. Only usage percentages sync, and sync can be turned off.

It reports to nobody

The app reports to nobody. It sends no telemetry in any mode. This website counts page views without cookies, which is a count of pages rather than a profile of you. Pro is optional and receives selected bounded quota snapshots after sign in. An API key is received only when you explicitly enable cloud metering, and only for that metering job.

Unknown stays unknown

A missing number never becomes a confident one. When a shape changes underneath a connector, that provider fails closed.

Lucas Costa

Author and maintainer. lucas@lucaswebsystems.com

GitHub SponsorsBuy me a coffeeRead the source