Repository navigation
v0.6.3 — a warning before the limit
The menu bar warns before a limit runs out
The rate-limit reading in the menu bar turns red at 90% — the same colour, at the same
threshold, as its row in the popover, now read from one constant so the two can never
disagree. Only the percentage changes colour, never the spend beside it.
It is on by default: a colour needs no permission and cannot interrupt, so there is
nothing to opt into. Menu Bar Shows → Colour the Limit at 90% turns it off.
90% was measured, not chosen. Against a month of real plan-usage history it flagged
every window that went on to run out, with the fewest false alarms of the rules tried —
including a cleverer one projecting whether a window would run out before its reset,
which did no better. No rule can warn more than about fifteen minutes ahead, because
Claude records usage only that often. The full reasoning is in
docs/design-budgets-and-alerts.md.
Claude Opus 5.5 is priced
It arrived unpriced, so its usage showed as —. It is now priced exactly as Anthropic
publishes it, as is Claude Fable 5.1. All twelve current Claude models match Anthropic's
pricing page exactly, including cache reads, which are most of a Claude Code bill and
which nothing previously checked. Opus 5.5 charges 0.05× input for cache reads rather
than the usual 0.1×; that was confirmed against Anthropic's own page before it shipped.
Three fixes make sure the new rates actually arrive:
- An upgrade now reaches people who have run
pricing refresh. A refreshed pricing
file used to win simply by existing, so an older one kept shadowing the newer rates an
upgrade shipped. The more recently generated snapshot now wins. - Retired models keep their rates. Moonshot retired its K2 generation. A model
leaving the catalogue does not change what its tokens cost while it was sold, so a
refresh now keeps those rates instead of retroactively blanking past costs. - A refresh can never price less than the install it replaces.
Also
macos/make-app.shrecognises the failure you get building on macOS 27 with only the
Command Line Tools — SwiftUI's macros ship only with Xcode — and prints the two
commands that fix it, instead of a wall of compiler errors.- CodeQL moves to v4 and
download-artifactto v8, both pinned to verified commit SHAs. - Two CodeQL notes cleared.
Full notes in CHANGELOG.md.
Upgrading
brew update && brew upgrade devopsinside/burn-o-meter/burn-o-meterThe menu bar colour is in the app bundle, not the CLI, so rebuild and reinstall the app:
git pull && macos/make-app.sh --install && open /Applications/burn-o-meter.appOn macOS 27 that needs full Xcode selected. The bundle is ad-hoc signed and still needs
Developer ID notarisation for distribution.