You are seeing a Pro account with available 5 hour refresh but still getting a 7 day wait or lockout. The root is a hidden weekly baseline limit or a brief Pro status sync issue that makes the app treat you like a Free tier user.
The Problem: Antigravity Pro says wait 7 days even with 5 hour refresh available
Antigravity Pro uses two quota layers. The rolling 5 hour pool refills on its own, but a 7 day baseline cap can override it and block access until the next week.
Some users also hit a tier misalignment bug where the IDE forgets Pro status, shows OAuth or Login errors in Output, and applies the weekly limit of the Free tier.
For background on how this dual quota works, see this short quota guide for Antigravity Pro.
Solution Overview
Aspect
Detail
Root Cause
Hidden 7 day baseline cap or a Pro token sync issue causing Free tier limits
Primary Fix
Re authenticate to restore Pro status, then manage usage via Quota Monitor and Usage Dashboard
Complexity
Easy
Estimated Time
5 to 15 minutes
Fix Antigravity Pro Quota Lock Now
Step by Step Solution
1. Check which quota actually blocked you
Open the Output tab in Antigravity.
Select Antigravity from the dropdown.
Look for messages like “Weekly baseline exhausted” or any “OAuth” or “Login” errors.
Open Agent Manager → Settings → Models and review the Model Quota Monitor. If Baseline Quota is low or empty, the 7 day cap is the blocker.
2. Fix the Pro tier misalignment
If Output shows “OAuth” or “Login” errors or your Baseline looks empty without heavy recent use:
In the Antigravity app, Sign Out.
Sign In again to refresh your Pro subscription tokens.
Re open Agent Manager → Settings → Models and confirm your Pro model is active and Baseline Quota now reflects your account.
For a quick refresher on subscription limits and what Pro unlocks, see our subscription quotas explained guide.
3. Protect your weekly baseline by switching models for light tasks
In Agent Manager → Settings → Models select Gemini 3 Flash for simple prompts like small explanations or single function help.
Keep Ultra or agent heavy models for larger changes only.
4. Stop agents that are burning quota without progress
If an agent keeps editing files without moving forward, cancel it.
Open the sidebar Activity or Account icon → Usage Dashboard → Detailed Logs or Quota Breakdown to see what used the most units.
Prioritize low cost actions and pause any long running Browser or Terminal sessions.
5. Schedule work around the rolling 5 hour tank
The 5 hour pool refills exactly 5 hours after the units were spent. If Baseline is still healthy, wait for that window to reset before running another big task.
Break big refactors into smaller batches to avoid draining both tanks at once.
If you need a deeper walkthrough of watching and pacing your spend, check our brief quota management tips.
Alternative Fixes & Workarounds
Wait for the next 7 day window
If Baseline is fully exhausted and re authentication did not help, you must wait for the weekly window to reset.
Reduce compute heavy features
Temporarily avoid Browser or Terminal runs unless required by the task.
Avoid external prompt chaining
Third party automation that triggers rapid prompts can trip abuse filters and cause an immediate 7 day lockout. Run Antigravity tasks directly from the IDE.
Use tab completion for free
Editor tab completion is usually not counted against Pro quota. Prefer this for small edits.
Troubleshooting Tips
If Weekly Baseline shows empty without heavy use, re check Output for “OAuth” or “Login” errors and Sign Out then Sign In.
Confirm you are actually on the intended Pro model in Agent Manager → Settings → Models.
In Usage Dashboard review high cost actions:
– Simple Chat is low weight
– Planning Mode is medium
– Multi file edits are high
– Browser or Terminal are very high
If an agent loops edits, stop it and restart with a narrower scope prompt.
If the IDE still shows Free tier limits after re authentication, clear app session cache and sign in again.
Best Practices
Watch the Model Quota Monitor before starting large edits so you know the state of both Sprint 5 hour units and the Weekly Baseline.
Scope tasks tightly. Ask for specific file or function changes instead of entire repository refactors.
Use the right model for the job. Keep Ultra for complex work and switch to Gemini 3 Flash for light tasks.
Review Detailed Logs weekly to spot patterns that drain your Baseline.
Avoid third party chaining to protect your account from automatic lockouts.
Most lockouts come from the 7 day Baseline cap or a brief Pro token sync issue. Re authenticate, check your Quota Monitor and Logs, and then shape your workflow to favor lower cost actions. This restores access quickly and keeps you productive without unexpected waits.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
