Repository navigation
feat(usage): Antigravity reports weekly limits for each model group #15299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
fdf3632
feat(usage): Antigravity reports weekly limits for each model group
Newarr a13dbd4
fix(usage): every Google sign-in refreshes Antigravity limits and ide…
Newarr 64bddfe
fix(usage): Antigravity limits always carry the Google account identity
Newarr f9b1beb
refactor(usage): send the decoded Antigravity credential as the refre…
Newarr 906dcd6
fix(usage): Antigravity 5-hour quotas show as session windows
Newarr e9782b2
Merge origin/main into feat/antigravity-usage-limits
Newarr File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Clear prior limits when sign-in replaces an authenticated account.
If the new account's refresh returns
probeFailed,onSessionStartedhas retained the prior account's limits andresolveUsageLimitsAfterProbekeeps them. Forking a refresh does not clear that state. Remove the prior limits on account replacement before starting the refresh. The earlier review requested this invalidation; the new callback adds only the refresh.🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not changed in this PR. The previous account's bars survive only when the new account's first quota read fails. The next successful read replaces them. Clearing them on that failure needs a change to the shared provider:
makeManagedServerProviderkeeps the last published limits onprobeFailedthroughresolveUsageLimitsAfterProbe. A failed read has no account identity to compare. That rule covers every provider, so I left it for maintainers instead of widening this PR.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Newarr, thanks for the clarification.makeManagedServerProviderretains the last published limits onprobeFailed, and a failed read provides no account identity to compare.The stale-account case remains unresolved. I understand your decision to leave the shared-provider behavior for maintainers rather than widen this PR.
Would you like me to open a follow-up GitHub issue for account-replacement invalidation?
✏️ Learnings added
🧠 Learnings used
You are interacting with an AI system.