Add usage-guard to Usage Analytics & Cost Tracking#809
Open
eltonylfgi-blip wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Description
Adds usage-guard to the Usage Analytics & Cost Tracking section. It is an open-source (MIT) Claude Code plugin that warns you in-session, before you hit your 5-hour or weekly quota, via a
Stophook that interrupts instead of waiting for you to glance at a status line. It shows an even-pace readout (ahead of or behind an even split of the week), exact % used with a reset countdown, a weighted burn-rate fallback, and a/usage-guard:usagecommand. Zero dependencies, local-only, no network calls.It sits alongside the existing quota and pace trackers already in that section (claude-lens, onWatch, WhereMyTokens); the differentiator is that it is a proactive in-session guard rather than a passive display. One-line addition, appended to the section like the neighbouring entries.
Checklist