feat: surface cache token usage in exec usage footer - #296
Merged
Conversation
exec's usage footer reported total in/out tokens but omitted cache read/write, unlike --print's footer which shows them. Track CacheReadTokens/CacheWriteTokens in the streaming loop and include a 'cache N read · M write' segment in the footer when nonzero, so cost-conscious exec users see prompt-caching savings. Footer still writes to stderr and honors --quiet. stream-json output is unchanged.
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
1 participant
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.
Summary
exec's usage footer reported total in/out tokens but omitted cache read/write, unlike--print's footer which shows them.Track
CacheReadTokens/CacheWriteTokensin the streaming loop and include acache N read · M writesegment in the footer when nonzero, so cost-consciousexecusers see prompt-caching savings. Footer still writes to stderr and honors--quiet.stream-jsonoutput is unchanged.Verification
go build ./...,go vet ./cmd/,gofumpt -lclean.go test ./...exit 0 (ran with-p 1due to shared-machine process pressure).