fix(vscode): make cache hit rate write-aware - #12738
Merged
Merged
Conversation
marius-kilocode
enabled auto-merge
July 31, 2026 14:05
chrarnoldus
approved these changes
Jul 31, 2026
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge The extracted Files Reviewed (4 files)
Reviewed by claude-opus-5 · Input: 20 · Output: 3.4K · Cached: 449.8K Review guidance: REVIEW.md from base branch |
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
fix(vscode): make cache hit rate write-aware
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 VS Code session usage bar currently calculates cache hit rate as cache reads divided by input plus cache reads. Because cache writes are excluded, sessions with significant write volume can display nearly 100% despite paying for millions of written tokens.
This changes the rate to include cache writes in the denominator, matching the write-aware calculation used by the TUI:
cache read / (input + cache read + cache write)The screenshots below use the exact same persisted session and token counts. The display changes from 100.0% to 49.7%, while
In 6,Cache R 19,242, andW 19,442remain unchanged.Before
After