v1.36.0 — the freshest sample wins, and the icon says where it came from
macOS build 72. The release is one idea: when an account has two sources, show whichever was measured more recently — and say where that number came from.
The freshest sample wins, local or cloud
The account row used to show the local value whenever one existed, no matter how old it was and no matter what the team cloud had just published. So this happened: someone refreshed on another Mac, and your side still showed this machine's cached number. The fact that someone had just used the account was invisible.
Now, for the same account and the same window, when both sides have data the later sample wins. That is what carrying the sample time was for. Without it the comparison was impossible and "local always" was the only available answer.
When either side has no time — an owner on an older build, or an endpoint that returns no timestamp — it stays local-first. "Cannot compare" is not "the cloud is newer", and presenting a possibly days-old cloud value as current is harder to explain than always-local.
Kimi, GLM and MiniMax carry a sample time too
All three were writing sampledAt: nil. It is the same omission that produced the future timestamp fixed last release, just on rows nobody happened to be watching.
None of their endpoints return a server timestamp, so the honest answer is the moment the response was decoded, taken once per response and shared by the rows and the enclosing UsageData, so the two cannot disagree by milliseconds. Without this, "take the newer" would have been a Codex-only behaviour and the feature would have looked broken everywhere else.
Provenance is no longer a new word — the icon already said it
The row used to read [icon] label · time · percent, where the label could be Local, Cloud, Latest or Mix. This release removes the last two.
They existed only to make provenance visible, and each one cost a reader a lookup before they could act on it. Mix was worse than that: nothing else in the app had ever taught the reader what a "mix" is, so the word had no intuition to rest on.
The icons already carry the same information: no icon means this Mac, a cloud means the team cloud, an eye means watched by address. So the row keeps the icon and the number, and the explanation moves into the tooltip, where it can be a sentence instead of a label: where the number came from, when it was measured, and — when both sources are involved — that the newer of the two is showing. That last one is not optional; without it a number that disagrees with the local one reads as a bug.
The local account still shows its source name (OAuth / Codex CLI). That one is not invented vocabulary — it is which credential this Mac is actually running on, and dropping it would lose information rather than remove noise.
Remaining percent without expanding
The account header now shows the selected cycle's remaining percent, so reading the number no longer requires expanding the account.
Which cycle is a choice is stored per account. Wanting 5h for one account and Weekly for another is the normal case, and a single global value means switching back and forth. With one cycle there is no switcher at all — a button with one option does nothing when pressed, and in the common weekly-only case the header already shows that number. With two cycles, a compact switcher appears under the header.
Before you have chosen, the row falls back to whichever cycle is currently running, so it self-corrects across a reset instead of pointing at a window that just closed.
This selection does not drive the menu bar ring. Those are two separate intents: the ring is a persistent display preference; this is "what did I want to read in this row just now".
The provider header stops spending a slot on a count
The header used to show 2/5 for Codex (how many accounts are still fresh) and 2/2 for everyone else (how many models still have quota). Two different meanings in one position, and neither is a question you ask daily — both are for troubleshooting.
It now shows when that section was last refreshed, plus the remaining percent of the current account. Current rather than aggregate, because that is the number the menu bar ring is already showing: the same app answering differently in two places is worse than showing one less number. With no local Codex account there is no "current" to speak of, so the percentage is omitted rather than picked arbitrarily — an arbitrary pick reads as a deliberate choice. A section that is entirely stale still shows its time: the newest timestamp would itself be old, and each row carries its own time regardless.
A horizontal reference line when hovering a cycle in deficit
The chart already draws a dashed diagonal for "where you would be at this rate if you burned evenly", but reading the overspend off it means eyeballing along a slope. A horizontal line from the hovered point to the right edge turns that into a distance you can read: where it meets the diagonal is how much of the window you have already spent early.
It only appears in deficit. On pace, the same line would suggest something is wrong when nothing is — and onTrack with a non-zero delta is still on pace, so the decision is made on the stage rather than the delta sign. Those two signs are opposite conventions in this codebase (UsagePace.deltaPercent is actual-minus-expected, currentIntervalPaceDeltaPercent is expected-minus-actual), so reading stage is what keeps this from coming out backwards.
The line uses the chart tint rather than a fixed green, which keeps it in the forecast family instead of reading as data, and it stays consistent with the curve when the curve itself has gone orange or red.
Smaller corrections
- Team member names are often email addresses and often longer than the space they get, so they now truncate at the tail instead of shrinking — a shrunken name makes that row read as if that member were special
- "Whole team" in the menu bar strip becomes "Whole". The old wording did not fit and pushed the selected member's name out of the visible area entirely, and that name is the one thing the control exists to show. It sits directly after the Team button, which is why the reader knows it means the team. The settings pickers keep the longer wording: they have the width, and they follow a subject-prefixed pattern there ("All devices", "All accounts")
- Groups with no account name — GLM and MiniMax when there is no local account name — no longer draw an account header at all. It rendered as
Local | Unknown account, where the source word was already in the section title and "Unknown account" only restated the absence. Zero information, one line of noise. Kimi drops out the same way when it has no account name
- MiniMax's subscription date drops the leading zeros:
2027-04-05 → 27/4/05. A renewal date answers "which day", and the right edge does not have the width to spare
Known boundaries
- The merge needs a sample time on both sides. An owner who has not updated keeps local-first, which is a deliberate conservative choice
- The horizontal reference line decides on the stage rather than the delta sign, because the two delta conventions in this codebase have opposite signs
- A local + cloud merged row renders only the winner, but it remembers that both sides took part (
mergedSourceKinds), which is what the tooltip reports