Repository navigation
Fix usage efficiency false positives - #205
Merged
Merged
Conversation
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.
Summary
Fixes
/usageefficiency false positives by only flagging repeated tool calls as waste when the same call repeats without an intervening mutating tool. This keeps legitimate edit→test and edit→diagnostics verification loops out of the waste estimate while still surfacing true idle duplicate calls.Also stabilizes popup width for scrollable
/usage-style panels so the floating popup no longer resizes or recenters when scrolling past longer text.Related issue
N/A
How was this tested?
go build ./cmd/yottacode— passesgo test ./internal/tui/... ./internal/agent/...— passesgo test ./...— passesgo vet ./...— cleanChecklist
go test ./...passesgo vet ./...is clean/usageUI behavior polish)