fix(elements): include reasoning and cache costs in context total - #462
Open
ephraimduncan wants to merge 1 commit into
Open
fix(elements): include reasoning and cache costs in context total#462ephraimduncan wants to merge 1 commit into
ephraimduncan wants to merge 1 commit into
Conversation
Contributor
|
@ephraimduncan is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
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
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.
The Context popover could show non-zero Reasoning and Cache line items directly above a "Total cost" that excluded both, so the visible breakdown didn't add up and users could underestimate a response's cost. The footer now prices the same four usage categories the row components display — input, output, reasoning tokens, and cached input reads — keeping all model-specific pricing in tokenlens rather than summing rounded strings.
Added a footer test using
vercel:xai/grok-3-mini-fast(a model that prices all four categories) with token counts sized so omitting any single category changes the cent-rounded rendered total; it fails against the previous footer, passes now, and also asserts the unrounded aggregate reconciles with the sum of the four per-row prices.