Your omp usage limits, right above the omp composer's context bar in Tern:
Tern's widget bar can show stats too, but it lives at the edge of the window. This sits right where you're already looking while you work: above the composer, every time you glance down, without leaving the session.
In the Spine chat style it sits just under the bar instead, on the composer's column, out of the way of omp's working status:
Hover it for each window's meter, reset time and saved resets:
What it does:
- follows your model: the active model's provider (anything
omp usagereports - Claude, Codex, Kimi, Gemini, Grok, Muse Code, …), switching within ~2 s of Alt+P, or to a subagent's model while you're viewing its transcript. New providers and windows just show up. - or every provider, or only the ones you pick, in your order
- several accounts on one provider: all of them (
Claude dev.ops 5H … · a.k.chen 5H …), only the one you pick, or combined into one set of windows. Switch any of them off to leave it out. - reads at a glance: a bar per window in its provider's colors, amber at 25% left, red at 10%. When a share changes,
a comet runs the bar to its new level. Saved resets show as
+N(+NFfor Claude's Fable resets). - a hover card that fits: you set how many rows it can take, and past that, accounts sum up instead of running off the screen
- quota details (Shift+Alt+U): every account and window in full, in a view of its own
- CLIProxyAPI and CPA Usage Keeper, if you use them: their accounts next to omp's own, with each account's plan, and from Keeper, the tokens and API-equivalent cost each window has used and roughly what's left
- the same numbers in every pane, even though every omp session checks usage on its own clock
- a settings panel (Ctrl+Alt+U) for what shows, the order, and each provider's windows and colors
- installs from Tern and sets up its own omp extension
- updates itself like Tern does: an Update omp Usage pill in the widget bar, one click to see what's new and install it. Nothing pops up over your work.
You need Tern with plugins on (Preferences › Plugins), and either omp signed in to an account with limits (omp usage should list them) or an external quota source.
-
Install the plugin. In Tern, go to Preferences › Plugins › Install, enter
github.com/jmazzola/tern-plugin-omp-usageand click Install. Or from a terminal:tern plugin install github.com/jmazzola/tern-plugin-omp-usage
A few seconds later it runs
omp plugin linkon itsomp/folder, so omp loads the extension as its own plugin,omp-usage, straight from the plugin's folder. Updates reach omp the same way. Then it tells you:
If it can't (usually because omp isn't on Tern's
PATH), it says that instead, and Tern's log has the reason and the exact command to run:
From then on it's one of omp's plugins:
/extensionsoromp plugin disable omp-usageturns it off,omp plugin enable omp-usageturns it back on. omp Usage leaves the link however you set it. If youomp plugin uninstall omp-usageand want it back, run omp Usage: Set up omp extension from Tern's palette. -
Turn on extension statuses in omp's bar, which is where the plugin reads the line from. Either:
# ~/.omp/agent/config.yml statusLine: showHookStatus: true
or, with
preset: custom, addstatustoleftSegments. -
Restart your omp sessions. Click into an omp pane and the line shows up above
1% ──── 1M(under it in Spine) within a few seconds.
To work on the plugin, clone the repo and link it instead, so Tern and omp load the files straight from your clone. Use forward slashes in paths, even on Windows.
git clone https://github.com/jmazzola/tern-plugin-omp-usage.git
cd tern-plugin-omp-usage
tern plugin link .Then have omp load the extension from the clone, and do steps 2 and 3 above:
omp plugin link ./ompNaming omp/extensions/usage-remaining.js under extensions: in ~/.omp/agent/config.yml works too. An installed
copy then skips linking its own, so omp never runs it twice.
Warning
The omp-usage folder is deprecated. Since 0.5.0 the plugin is the repo itself. Clones linked to
…/tern-plugin-omp-usage/omp-usage (the old install) relink to the repo folder on their own when they update to
0.5.0, and a toast says so:
If that fails, a toast tells you where to run tern plugin link . yourself:
The folder goes away in a later release, and a clone still linked to it stops loading then. tern plugin list
shows which folder yours is using.
Each provider gets its label, then each window gets its label, a bar filled to the share left, the share, and a
countdown to its reset. Saved resets come after as +N (+NF for Claude's Fable resets), and any other statuses
omp's extensions set go last.
A window at 25% left or less turns amber, and at 10% or less, red. When a share actually changes, the line prints again while a comet runs the bar to its new level: in the provider's color when quota went down, green when it came back. With Reduce Motion on (Tern's or the system's), nothing moves.
Hover the line and after a beat the card opens: a row and a meter per window, its reset countdown and clock time, when
each saved reset expires, and the other statuses. The last row names the shortcuts for the quota details and the
settings. The card can take up to the number of rows you set in the panel (26 by default). Past that, accounts sum up
to a row each, and then the last few fold into one (+4 more accounts · lowest 7D 5%).
A CLIProxyAPI or Keeper account also gets its plan as a pill on its heading, and where Keeper has an estimate, the tokens and API-equivalent value left go under the window's bar:
Clicking the line does nothing - it's drawn over omp's composer, and Tern doesn't give plugins clicks there. Use the
shortcuts, or usage in the widget bar.
Every account and window in full, in a view of its own, with no row limit. Open it with:
- Shift+Alt+U (rebind
plugin.omp-usage.details) usagein the widget bar. Tern only shows plugin segments in its Plugin segments widget, which you have to place yourself (palette › Edit widgets…), andusageshows there while an omp pane has focus.- Quota details at the end of the settings panel's bottom bar
- omp Usage: Quota details in the palette
It opens over the tab. Click outside it or press Esc to close it, or drag its header to keep it around. Settings swaps it for the settings panel (and the panel's Quota details swaps right back); Close closes it.
Each provider or account gets a heading in its own color, then a box per window, side by side while they fit: the share, a bar in the line's colors, and its resets and notes. A window running low is ringed amber, and red when it's nearly empty. It always shows the same providers, accounts and windows as the line.
With a CLIProxyAPI or Keeper source, each account's heading also gets its plan as a chip and when its numbers were observed, notes call out a stale or failing source, and windows Keeper has usage for get Observed usage and Estimated remaining under the bar. Here it is with sample data shaped like a Keeper source's, in Tern's Titanium dark theme:
Open the panel with Ctrl+Alt+U (rebind plugin.omp-usage.panel), Settings in the quota details, or omp Usage:
Settings panel in the palette. Changes apply right away, in every window.
| Section | What it does |
|---|---|
| Preview | The line and its card, drawn for the last omp pane you used. Under it, Card height: 16 to 50 rows, 26 by default. An estimate under a bar takes a row; everything else Keeper reports goes in the quota details |
| Show | Current model (default), All providers (countdowns move to the card), or Selected providers. When there's no quota data for them, the line falls back to the focused session's own status |
| Providers | Pick a row up by its grip, then click where it goes. Click a window to hide or show it everywhere. The switch adds the provider to Selected. With several accounts, each one gets its own row: grip, name (click it to show only that account, again for all), windows, and a switch that takes it off the line, the card and the quota details. A chip next to the provider says what's showing, with a button for the next option: all 8 accounts with combine, combined · 10 accounts ✕ with by plan, by plan · 6 with 5H, 4 without ✕ with all in one, or only dev.ops ✕. By plan, each account's row is tagged with its group (5H, no 5H) |
| Colors | A preset, a named alternative (Ember, Sunset, Moss, Ocean, Orchid, Slate, Theme accent), or Custom… hex colors (#d97757, or two: #9aa7b4, #5b8def) |
| Updates | Status, Check for Updates or Download Update, and how often to check (see Update) |
External quota sources are set up in a file, not the panel (see External quota sources). Their accounts show up under Providers like omp's own.
Prefer the keyboard? omp Usage: Settings… in the palette has all the same options as menus.
All providers, one after another. Muse Code's 5-hour window has turned amber:
Selected providers, here Codex and Muse while an Opus model is in use:
Colors, with Claude on Sunset and Codex on a custom #22d3ee, #a78bfa:
Accounts go by the part of their email before the @. Seats that share one add their domain (claude-team@lumen,
claude-team@pinegg).
Here are ten Claude accounts, two of them switched off. The line starts with the first account. The card shows the first accounts' windows in full for as long as they fit your card height, then sums up each of the others in a row, and with even more, folds the last of those rows into one:
In the panel, click an account's name to show only that one (click it again, or the chip next to the provider, to go back to all of them). The switches take accounts off the line and the card:
That gives the line room for all of that account's windows, and the card sums up the others in a row each:
Combine shows all of a provider's accounts as one: each window's share is the average of the accounts that have it, its reset is the soonest one, and its saved resets are all of theirs added up. A window only some of the accounts have says how many:
By plan groups the accounts that have the same windows instead. omp doesn't say which plan an account is on, so the windows are what tell them apart. Here, 6 accounts have a 5-hour window and 4 don't:
In the panel, the chip says how they split, and each account's row says which group it landed in:
Combining only averages shares. Tokens, costs and estimates are never averaged or added up across accounts (that would be meaningless across different plans), so they only show with All accounts or a single account picked.
To reorder, pick an account (or a provider) up by its grip. It lifts, every spot it can go opens up, and a click drops it there. Its grip turns into a cross, which puts it back:
omp Usage: Settings… › Provider accounts… does the same thing from the palette, as menus:
On top of omp's own accounts, omp Usage can show the accounts behind two proxies, each source as its own provider
and account pool (Codex@dashboard):
- CLIProxyAPI (CPA): quotas read through its management API, with each account's plan
- CPA Usage Keeper: quotas from its cache. Keeper also records every request CPA serves, so for a window with usage it knows the tokens and API-equivalent cost spent so far, and omp Usage estimates what's left from that.
Set them up in ~/.omp/agent/usage-sources.json and restart your omp sessions. Nothing changes until that file
exists. The settings, model mappings, what each source can and can't give you, and what the views show are all in
docs/quota-sources.md.
The plugin checks its repo every 6 hours (or Hourly, Daily, Weekly, or Off in the panel): a clone checks its remote, and an installed copy checks a copy of the repo it keeps in its data folder. When there's a new version, a toast says so once, and an Update omp Usage pill sits in the widget bar until you deal with it:
The pill and usage are plugin segments, so they only show while the widget bar has its Plugin segments widget
(palette › Edit widgets…).
Click the pill (or Check for Updates) for the update card at the top of this page: the version that's out, the one you have, and every new commit in full.
| Button | What it does |
|---|---|
| Download Update | Brings the plugin (and an installed copy's omp extension) up to date and reloads it. The toast says if omp sessions need a restart |
| Skip This Version | Hides the pill until the next plugin change |
| Not Now / Esc | Closes the card. The pill stays |
Open settings panels step aside while the update lands, so nothing flashes half-drawn:
When omp's link to the extension has to change, it tells you. That's the first time 0.7.0 or later loads after an
update (which also deletes the ~/.omp/agent/extensions/usage-remaining.js loader that 0.5.2 to 0.6.x wrote), or
after the plugin's folder moved:
A few things to know:
- commits that only touch the README,
docs/or.omp/don't count. They don't light the pill, and come along with the next real update. - a merged pull request shows up as one entry (its merge), not every commit in it
- it never merges or rebases your work in a clone. With local commits, or edits in the way, update by hand:
git pull, thentern plugin reload. - clones linked to the deprecated
omp-usagefolder relink to the repo folder when they update (see From a clone) - updates need git on your
PATH, installed copies included - an installed copy updates from whatever repo its
upstreamfile names, read on every check. A fork puts its own URL there, and updates leave that file alone.
| To | Installed | From a clone |
|---|---|---|
| Turn the plugin off | Preferences › Plugins | tern plugin unlink omp-usage, or Preferences › Plugins |
| Turn it back on | Preferences › Plugins | tern plugin link . from the repo folder |
| Turn just the extension off | omp plugin disable omp-usage (or /extensions in omp), then restart omp |
The same, if you linked it. Otherwise delete its line from ~/.omp/agent/config.yml |
| Remove it | omp plugin uninstall omp-usage, then tern plugin remove omp-usage, and restart omp |
omp plugin uninstall omp-usage (or delete the extension's line from ~/.omp/agent/config.yml), then tern plugin unlink omp-usage, and restart omp |
| Symptom | Check |
|---|---|
tern plugin list isn't ready |
It prints the error. Tern's log is at %LOCALAPPDATA%\Tern\Logs\tern.log |
| No line | The focused pane is omp; its provider has limits; omp was restarted after installing; extension statuses are on (step 2); omp plugin list shows omp-usage enabled (if not, run omp Usage: Set up omp extension from the palette), or extensions: in config.yml names it |
omp Usage couldn't set up its omp extension |
Tern couldn't run omp plugin, so omp has to be on the PATH Tern started with. Tern's log has omp's reason and the omp plugin link … command to run yourself |
| All/Selected only show the current model, or panes show different numbers | The cache is stale. Restart your omp sessions |
| The card's reset dates flip between two values | An omp session from before an update is still writing the cache. Restart your omp sessions |
| The line stopped after an omp or Tern update | omp may have renamed something the plugin reads. Ask omp to fix omp-usage |
| Clicking the line does nothing | That's expected: Tern doesn't give plugins clicks on omp's composer. Use the shortcuts, or usage in the widget bar |
| Shift+Alt+U or Ctrl+Alt+U does nothing | Another binding took it. Bind plugin.omp-usage.details or plugin.omp-usage.panel to something else |
No update pill, or no usage |
Add the Plugin segments widget to Tern's widget bar (palette › Edit widgets…), or use the panel's Updates section. Checks might also be Off |
omp Usage can't check for updates |
It needs git on PATH; a clone needs a branch tracking a remote, and an installed copy needs its upstream file naming the repo (https://github.com/jmazzola/tern-plugin-omp-usage.git). The toast gives the reason |
omp Usage can't tell which version it is |
The repo its upstream file names has no commit at the installed version. A fork has to put its own URL in upstream |
omp Usage couldn't link its repo's root |
It's a clone linked to the deprecated omp-usage folder. Run tern plugin link . in the repo folder |
Edits to the plugin's .luau files don't show |
tern plugin reload |
Don't edit Tern's settings.json from PowerShell: it adds a BOM, and Tern falls back to its defaults. For external
quota sources, see their troubleshooting.
The parts, the cache every pane reads, the tests, and what it's been tested with: docs/development.md.




















