An agent’s usage share is not its subscription quota
Why a percentage can fall while an agent keeps working, and how to read harness shares and account limits correctly.
A dashboard can show an agent falling from 60% to 40% even while its token counter rises. That is possible when the percentage measures its share of a growing total. It is misleading when the interface makes that share look like remaining subscription capacity.
The fix starts with the denominator. Every percentage needs to answer “a percentage of what?” before it can support an operational decision.
Compare like harnesses
Consider an illustrative Claude group with two Agents. One has $12 of tracked list-price usage and the other has $8. Their shares are 60% and 40%. If the second grows to $18 while the first stays at $12, the first Agent's share falls to 40%. No tokens were removed and no subscription capacity was restored.
In FlockTab's overview, subscription shares are grouped by harness. Codex activity should affect the Codex comparison, not the Claude comparison. Hiding a card should not change the underlying population either; otherwise a filter silently rewrites the meaning of every bar.
Read quota at the account level
Provider-reported quota answers a different question: how much of an account's allowance has been consumed in a particular vendor window? That reading may include other Agents, another machine, or usage outside FlockTab. It belongs beside the account identity, window, reset time, and observation time.
A daily reporting window in your dashboard does not turn a provider's weekly limit into a daily one. Two percentages from different windows should remain separate. When quota is unavailable, show the measured activity and the missing observation rather than deriving an allowance from a subscription's monthly price.
Use each view for its own decision
Use harness shares to find which projects are driving tracked activity in a particular tool. Use account quota to decide whether a login is close to a limit. Use the provider's bill or plan charge to understand actual expenditure. These views can all be correct while displaying different dollar amounts or percentages.
For example, an Agent could be the only Grok Agent tracked and therefore show 100% of Grok usage. That does not mean the account is exhausted. It means the observed comparison group has one contributor. A useful tooltip or adjacent label makes that fact clear without requiring the reader to reverse-engineer the chart.
Ask for a denominator audit
When reviewing a cost dashboard, select one Agent and write down its numerator, denominator, time window, and source. Then change a filter and verify whether those definitions remain stable. Repeat with a second harness and a second account.
FlockTab separates the Agent's recorded usage from the account's reported quota. The practical habit is equally useful elsewhere: when two bars appear related, first verify that they actually describe the same population and allowance.
Reference: FlockTab: command reference and setup
Sources checked 23 September 2026. Numerical scenarios are illustrative unless explicitly identified as provider data. Vendor limits and interfaces can change; consult the linked documentation for current details.