v0.6.2

The menu bar app: a subscription's details say what they know

A click on a subscription in Limits opens its details. They already said who spent the window, where it is headed, and how old the reading is, but the app worked out the window's start on its own, and every subscription had a line about its reading, even a fresh one this Mac took. Now each line comes from the report, and the reading's line shows only when it tells you something.

• This window. Who spent the main window since it began, by the team's weighted tokens: the two busiest devices, then the rest as a count, "build-01 84M, scout 35M, +8 more · since 21 Sep 02:40", where it said "+8" after the second device. When the line has no room, it drops the start first, then the second device, "build-01 84M, +9 more", and its tooltip still names every device. Alone, it says the tokens, "102M · since 20 Sep 01:00". The start is now the report's, the time it counts those tokens from, where the app worked it out on its own.
• Forecast. The window that runs out, where it is headed by its reset and the pace that takes it there, "164% at reset · this week's pace", as before. For a forecast that stopped, as v0.6.1 has it, where nobody on the team has spent on the subscription since it would have run out, it now says where the window was headed, "would reach 108% at reset · this week's pace", and no longer reads as a window still on its way there.
• Last used. When anyone on the team last used the subscription, "20m ago", as before.
• Reading. How old the reading is and which device took it, "4m old, from scout (hermes)", now only when that says something: the reading is stale, another device took it, it came through another login, or a stopped forecast stands on it. A fresh reading this Mac took has no line. A stale reading's age is still in yellow.

See the details of the demo team's Codex bots, whose reading another device took. The README's Menu bar app has the picture in dark and light.

JSON: the window's start and the reading's device

The report adds two fields, so that the app shows the report's answers instead of working them out again:

• window_start on each column of team.matrix: when the main window began, the time its window_tokens and window_burn count from. It is null when no main window is known: for a column of tokens no subscription covers, a subscription with no reading of its main window, or one whose window has reset since the reading.
• device_id on a team account's quota: the id of the device whose reading is newest, as a team device's device has it, beside device, its name. A reader tells this device's reading from another's by it.

No field changed meaning, so the schema version stays 4. A report from an earlier release has neither field; read them as null. ai-usage report --from does not fill them in. See docs/json-schema.md.

Compatibility and upgrade

What to do. Nothing. Releases from v0.2.5 on install v0.6.2 within 15 minutes, and on a Mac the menu bar app updates with the binary and restarts into it.

What changed. The menu bar app's details of a subscription, and the two fields of the JSON. The console's report, ATTENTION, the forecasts, the snapshot, and the relay are as in v0.6.1. This Mac's ai-usage works out both fields from what its teammates already send, so they need not update for them, whatever release they run.

macOS 27. As in v0.6.1, an update that a run you start installs, such as ai-usage update or the app's Check for Updates, costs no scheduled run. One that a scheduled run installs costs the next scheduled run, which any ai-usage you start, or the app's next read of the report, makes up.

State. Nothing changes in the state folder or the snapshot, and the app keeps its settings.

Known limitations

• A menu bar app from v0.6.1 shows its details as before, a line about every reading and a stopped forecast's "108% at reset", until it updates: for the moment between the binary's update and the app's, or, when the app's update fails to install, until it is downloaded again 6 hours later.
• The app shows what the command-line tool's report has. When the tool is another release before v0.6.2, as Settings' About says, the details have no start, and a team's reading names its device even when it is this Mac's and fresh.
• This window counts what the team's devices sent, as of each one's last report. Spend from outside the team, such as on the web or on a machine without ai-usage, is not in it.
• The macOS 27 limitations of v0.5.1 stand: after a scheduled run installs a release, launchd still refuses the next scheduled run, and a run you start, or the app's next read of the report, makes it up.

What's Changed

• Menu bar app: who spent the window, last used, and where the reading is from by @neoromantic in #21

Full Changelog: v0.6.1...v0.6.2