Repository navigation
fix(web): recalculate cache token price estimates - #812
Merged
Merged
Conversation
|
You have reached your Codex usage limits for security reviews. Please try again later. |
This was referenced Oct 11, 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
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 model price editor showed separate text, image and audio cache inputs, but a pricing expression using the generic
crvariable ignored those counts. The estimate now uses the same effective cache total for bothcrand tier selection, and updates as the inputs change.Validated locally at
2c53f147fa755fe715d033c15a67a8a782b3ce69: the interaction regression failed before the fix; 41 tests across seven pricing files, frontend type checking, and changed-file lint/format checks pass. This changes the frontend estimate only. The final combined release build and production verification are pending.