Update plugin entry: usage-tracker - #175
Open
MateoCerquetella wants to merge 1 commit into
Open
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.
What changed
Usage Tracker now shows Codex, Claude Code, Grok, and OpenCode usage. When more than two providers are enabled, the sidebar keeps a compact highest-usage summary with a
+Ncount; selecting it opens the full provider overview. Usage turns yellow at 80% and red at 95%.This marketplace update refreshes the description and tags, raises the tracked Git release range to
^0.1.6, and vendors the current Usage Tracker icon.Release source
https://github.com/MateoCerquetella/bb-plugins.gitplugins/usage-trackerusage-tracker/^0.1.6usage-tracker/v0.1.6Validation
Permissions and security
Usage Tracker requests no additional declared permissions and adds no external service integration. It reads BB's provider-usage response, validates it at the RPC boundary, and displays provider-local usage or recovery status. No credentials are included in the marketplace entry or icon.