feat(ui): the Overview cards say what kind of money they are, in order - #52
Closed
as-koshiyama wants to merge 4 commits into
Closed
feat(ui): the Overview cards say what kind of money they are, in order#52as-koshiyama wants to merge 4 commits into
as-koshiyama wants to merge 4 commits into
Conversation
# Conflicts: # CHANGELOG.md # src/ui/mod.rs
SPEND, TOKENS, TOKEN COST, AVG USAGE RATE, TOOLS & SITES - the actual bill first, the work done, the API-rate hypothetical it would have cost, how hard the plan is being driven, the machine's inventory last. SPEND now carries only real money: the saving-vs-API-rates line moves off it (that comparison lives on TOKEN COST and in the Cost view) and in its place the card says whether extra usage is in play, from the metering samples - 'no extra usage' while no window has ever pegged, 'extra usage likely' once one has, and nothing claimed on a machine without history. AVG USAGE RATE is new: the mean peak of the 5-hour windows, the number that predicts a cap hit before it bills, with the hottest window amber from 90% and a pointer to the per-day breakdown on [m]. TOOLS and AI SITES fold into one inventory card. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
kleyt0n
changed the base branch from
feat/spend-vs-token-cost
to
feat/metering-view
August 3, 2026 10:29
Contributor
Author
This was referenced Aug 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The Overview cards reorder to say what kind of money each one is, left to right: SPEND, TOKENS, TOKEN COST, AVG USAGE RATE, TOOLS & SITES — the actual bill first, the work done, the API-rate hypothetical it would have cost, how hard the plan is being driven, the machine's inventory last.
SPEND carries only real money now
The saving-vs-API-rates line moves off the SPEND card — that comparison is the hypothetical's business, and it lives on TOKEN COST and in the Cost view. In its place the card answers the question actual spend turns on: is overflow billing in play? Driven by the metering samples, in the honest grammar:
no extra usage— the windows have never pegged (extra usage bills only past 100%).▲ extra usage likely+ amber — a window has pegged (the conservative trigger from feat(cost): surface extra-usage and credit consumption in the SPEND display #50's design).Two tests pin that no
API ratesstring can appear on the Overview when SPEND renders with figures (the phrase only ever comes from TOKEN COST's own qualifier).AVG USAGE RATE is new
The mean peak of the 5-hour metering windows — the number that predicts a cap hit before it bills, which no token count can. Qualifiers: window count, hottest window (
▲amber from 90%), and the[m]pointer to the per-day breakdown on Usage. Shows–with the absence stated on machines without Claude Desktop's samples.TOOLS & SITES fold into one card
9 · 12-style headline, keeping the▲ autonomousand▲ browser(s) unreadablewarnings and the visit total. Both cfg variants handled (non-sqlite builds say sites are not compiled in).Verification
Three new tests (extra-usage line follows the meter through quiet → pegged; AVG USAGE RATE averages peaks and states absence; the folded card exists and
AI SITESis gone) plus the no-API-rates-on-SPEND assertions.cargo fmt,clippy -D warnings, 268 tests pass on the branch. Docs: the Overview card table and order rationale indashboard.md; CHANGELOG entry included.🤖 Generated with Claude Code