fix(vscode): correct cache token indicator#12211
Merged
Merged
Conversation
(cherry picked from commit 8862283)
5 tasks
marius-kilocode
enabled auto-merge
July 14, 2026 15:56
chrarnoldus
approved these changes
Jul 14, 2026
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (3 files)
Reviewed by gpt-5.6-sol · Input: 86.5K · Output: 4.2K · Cached: 322.3K Review guidance: REVIEW.md from base branch |
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
3 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.
Supersedes #12170 by @mjnaderi. Full credit to Mohammad Javad Naderi for the original work; the feature commit was cherry-picked with original authorship preserved.
The original PR came from a fork, so the Visual Regression workflow could not auto-commit the updated screenshot baselines. This org-owned branch lets CI regenerate them.
Context
Cached tokens are cache-read prompt tokens, so they belong to the input side of token usage. The summary previously showed them with the output/down-arrow icon and placed them after output, which made the token flow misleading.
Implementation
The compact token summary now renders cache reads with the input/up-arrow icon and orders the values as fresh input, cached input, then generated output. A patch changeset is included because this corrects user-visible token usage information.