Reading the quota panel

The Report destination and the commands behind it. What each word in the subscription row means, in the terms the source defines, and what changes between the panel, the report and autodev quota.

Where it is #

The panel's Report destination holds it. autodev report prints the same model in a terminal, for the last 12 hours unless --hours says otherwise, and --json prints it as JSON. autodev quota prints the quota half on its own, for the last 7 days unless --days says otherwise. Every CLI command describes both.

The report covers this project. autodev quota covers every project on the machine, because a subscription is shared by all of them.

What the report holds #

The report reads, top to bottom:

• Status. A grid of status, daemon, iteration and est. cost. Above it, one line gives the reason for the state: alive for a live run, and for a stopped one the last event that ended something. est. cost is an estimate the run keeps: real billing for an API user, an estimate for a plan user.
• Needs you. What is waiting on a person, the same items as the status bar. The run stopped and why covers them.
• Activity. Only when nothing ran in the window, it says so. An empty night is a result, not a blank page.
• Done and Blocked. The tasks and commits in the window, with the most recent titles, and counts of the errors that were retried. In the panel, the count of errors is a button that opens Needs you.
• Subscription. The bar and the three figures below.
• Quota. One row per provider, then a chart.
• Two lines about failover, when they apply.
• Other workspaces. The other projects on the machine.

The subscription row #

The row has four words: subscribed, used, idle and converted. The source defines each one, and none of them is a measure of tokens or of a plan's allowance:

In the panel, the window's label sits above one bar with the subscribed time at its right. The bar has two widths, used and idle, and the idle part is hatched, because it stands for an absence. converted, used and idle are the three figures under the bar. autodev report prints the four words on one line.

So idle says how long the subscription sat with no agent running. It does not say how much of an allowance was left unspent. What is measured says what each word is derived from.

Per provider #

Each provider has a row. It opens with the provider's name and a verdict, limit crossed when the provider reported a usage limit in the window, no limit hit when it did not. Under it are four figures. commits is the commits recorded for that provider. turns is its calls. held is its agent time, which is the sum of the durations of its calls, so two calls that ran at once add up. limits crossed is the usage limits it reported.

Providers are never merged into one row, because a limit belongs to one subscription.

The chart #

The chart has one bar for each local day that had a call, a commit or a limit. A bar's height is the share of that day's own time in which anything ran. The day's own length is the divisor, so a first or last day that the window cuts short, and a day that is longer or shorter because of a clock change, are not drawn wrong. A day that crossed a limit takes the warning colour. Hovering a bar gives the day, the time busy, the commits and the limits.

A day with nothing on it is not drawn, and the subscription row still counts it as idle.

Failover and other workspaces #

Two lines can follow the chart. <n> failover(s) kept the run moving counts the times a participant moved along its failover list. A teammate taking a limited turn is not counted in it. <n> time(s) every provider was limited at once counts the times the whole team was limited together and the run waited for the first return.

Under Other workspaces, each other project has a mark for whether its run is alive, its name, its status and its commits in the window. A status that claims a run is active while no daemon is alive reads (stale). Projects with no activity are counted, not listed.

In a terminal #

autodev quota prints three parts, and a fourth when something is wrong:

• Providers, with each one's calls, agent time, commits and limits. A provider that declares it reports quota and sent none shows no quota reported (expected) as a warning. Each row also carries the number of inferences, the model calls a turn made, or inferences unknown when the CLI does not say, and the largest context any call of the period ran on, as peak context.
• Totals: agent time, and the share of the window that was occupied and idle.
• Windows, per provider and per window kind, never combined. Each shows the highest utilisation the provider reported, what that leaves, the commits inside the window, and exhausted when a limit was recorded inside it. Here idle is the part of the window's allowance the peak did not reach, which makes it the one place the word is about the allowance rather than about time. Only a five-hour window has ever been captured, and only claude sends the figures.
• Integrity, when lines of the ledger cannot be read, a record has a timestamp that is not a date, a snapshot has no reset time, or a call carries a context window its provider does not declare. A damaged file does not read as a quiet month.

--series prints the same ledger per local day and per provider.

Where the ledger lives describes the file the panel reads.