Fix Cursor plan percent calculation#282
Closed
Hilo-Hilo wants to merge 1 commit intosteipete:mainfrom
Closed
Conversation
Cursor’s /api/usage-summary breakdown fields describe used spend, not the plan limit. Compute plan percent used from used + remaining (fall back to limit) to avoid showing 0% left.
Collaborator
|
Thanks for the PR! We merged #240, which fixes the Cursor plan percent/limit bug by using |
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
2 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.
Summary
used + remaining(fallback:limit) instead ofplan.breakdown.total.0% leftwhen breakdown fields reflect used spend.Test plan
./Scripts/compile_and_run.shCodexBarCLI usage --provider cursor(Cursor Ultra now reports ~60% remaining instead of 0%).