Files

T

David Heinemeier HanssonandClaude Opus 5 24dc914d28 Recover model-usage limits from a boot-time probe failure

The shell starts before DHCP finishes, so Claude's first probe of the
OAuth usage endpoint came back as a transport failure and pinned "Claude
limits unavailable" for a full refresh interval. Opening the panel could
not clear it either: the open path refreshed unforced and hit the same
throttle it was trying to escape.

A transport failure now arms a short retry that goes straight to the
probe, since a retry answering to the throttle never gets off the
ground. Any real answer disarms it — a server that replied, 429
included, is one to stop pestering. Probes are single-flight, a fresh
token skips the throttle its predecessor set, and opening the panel asks
for the wire without re-walking every transcript on disk.

The module also earns its place in the bar now instead of sitting there
dimmed with nothing to say: it collapses out entirely until a provider
has actually recorded usage, here or on a synced machine. That made both
presence probes redundant, so they are gone. Selection follows the
provider rather than its slot, so one appearing while the panel is open
no longer swaps out what you were reading.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-07-28 11:00:43 -07:00

4.2 KiB

Raw Blame History

Model usage

One bar icon and one panel for every AI coding subscription on the machine. Panel.qml owns the bar button and the popup; Main.qml owns provider fan-out and the optional cross-device aggregation; providers/ holds one adapter per subscription.

Panel

Hero — the mark, the tool, and the plan it runs on ("Max 20x", "Pro"). Auth and endpoint problems replace the plan line and repeat in a card.
Subscription switch — one chip per enabled provider (h/l or click). It appears only when more than one provider is enabled.
Limits — a meter per window (session, weekly). The notch on the meter marks where an evenly paced window would have you right now, so the gap between the fill and the notch is the whole story: fill behind the notch means budget in reserve, fill past it means you are burning faster than the clock and the row says when it runs out.
Usage this week — one row per day for the last week: day, bar, tokens, with today bolded at the bottom. Hover today for its prompt and session count.
Usage by model — total tokens and active days in the header, then tokens per model with the bar behind each row showing its share of the heaviest one. Hover for the input / output / cache split.

A subscription appears only when it is enabled in settings and has actually recorded usage — on this machine or on a synced one. With one such provider there is no switch row at all; with none, the module leaves the bar entirely rather than sitting there with nothing to say. A CLI installed mid-session shows up at the next refresh, so nothing polls the disk waiting for it.

Providers

Provider	Limits	Local stats
`claude`	Anthropic's OAuth usage endpoint (5-hour session + 7-day weekly)	`~/.claude/projects` scanned by `scripts/claude_usage_scanner.py`, plus `stats-cache.json` and `history.jsonl`
`codex`	`scripts/codex_usage_scanner.py` reading the Codex CLI state	the same scanner

Claude limits need a signed-in CLI; without credentials the panel says so and falls back to local stats only.

Interactions

Bar icon: left = panel, right = refresh, middle = next subscription.
Panel: h/l switch subscription, j/k scroll, r or Enter refresh, Tab moves to the neighboring bar panel, Esc closes.
IPC: omarchy-shell omarchy.model-usage <open|close|toggle|refresh|next>.

Settings

Settings live in the widget's entry in ~/.config/omarchy/shell.json. The top-level keys can be set with omarchy bar plugin set omarchy.model-usage <key> <value>:

Key	Default	What it does
`refreshIntervalSec`	`900`	How often local scans and snapshots refresh
`syncMode`	`"Off"`	`"On"` writes this machine's snapshot and merges the others
`syncDir`	`""`	A folder synced by Syncthing, Dropbox, rsync, …
`syncFileName`	`<hostname>.json`	This machine's snapshot file
`syncDeviceId`	hostname	Stable device name inside the snapshot

Numbers need --json, or they land in shell.json as strings:

omarchy bar plugin set omarchy.model-usage refreshIntervalSec 300 --json
omarchy bar plugin set omarchy.model-usage syncDir '~/Sync/model-usage'

Per-provider settings are nested, and set writes its key literally rather than walking a dotted path — so pass the whole providers object as JSON (or edit shell.json directly):

omarchy bar plugin set omarchy.model-usage providers '{
  "claude": {
    "enabled": true,
    "statsPath": "~/.claude/stats-cache.json",
    "credentialsPath": "~/.claude/.credentials.json",
    "projectsPath": "~/.claude/projects"
  },
  "codex": { "enabled": false }
}' --json

enabled defaults to true for both; set it to false to hide a subscription that is installed. The paths above are the defaults.

With syncMode on, every *.json snapshot in syncDir is merged, so today, the last 7 days, and the all-time totals cover every machine you code on — active days are unioned by date rather than summed. Rate limits stay per-account and are never merged.

One caveat on "all-time": the Codex scanner only reads native session files touched in the last 30 days, so Codex totals and its day count cover that window. Claude's cover every transcript still on disk.

4.2 KiB Raw Blame History