You reset the 5 hour quota in Google Antigravity but you still get multi day lock messages. The cause is a new weekly limit and the AI Credits setting that burns through usage quickly.

Fix Google Antigravity weekly quota lock after 5 hour reset

Users report that even after the familiar 5 hour reset, Antigravity still shows a lockout with messages like a 6 to 7 day wait. The new quota model introduces a weekly limit on top of the short reset window, and enabling AI Credits can multiply consumption for heavier tasks which drains the weekly pool almost instantly. If AI Credits are on, a few heavy prompts can zero your week. Turning Credits off or temporarily downgrading to a build without that feature are the most direct fixes.

Solution Overview

Aspect	Detail
Root Cause	New weekly quota layered over the 5 hour reset and AI Credits causing accelerated consumption on heavy tasks
Primary Fix	Turn off AI Credits in Antigravity settings, then use lighter prompts; if needed, downgrade to a prior build without Credits
Complexity	Easy for settings change, Medium for downgrade
Estimated Time	2 to 5 minutes for settings, 10 to 20 minutes for downgrade

For a deeper look at how plan tiers and usage pools interact, see this breakdown of Antigravity subscription quotas.

Fix the weekly quota lock immediately

Step by Step Solution

Step 1 Turn off AI Credits in Antigravity

• Open Antigravity.
• Open Settings then find Usage or Billing.
• Locate AI Credits and switch it off.
• Restart Antigravity to ensure the toggle is applied.
• Test with a single light prompt to confirm usage no longer drains rapidly.

Tip: Some builds show Credits under Account or Plan. If you cannot find the toggle, proceed to Step 3 to install a version without Credits. Step 2 Reduce prompt cost to stretch the weekly pool

• Prefer concise prompts. Avoid very long system instructions and massive context blocks.
• Avoid batch jobs and tool chains that fan out many sub tasks.
• Use smaller result sizes or lower output tokens if the product allows setting them.
• Run one heavy job at a time and pause background automations.

Reference on general model quotas and pricing: Google AI usage and pricing and Gemini API quotas. Step 3 Downgrade to a build without AI Credits

• Back up your Antigravity project files or workspace.
• Uninstall the current Antigravity app.
• Clear app cache and config to remove residual Credits flags. Use these platform specific commands, then reinstall an older build from the official releases page.

Windows PowerShell

# Close Antigravity first
Get-Process Antigravity -ErrorAction SilentlyContinue | Stop-Process

Remove app data folders
Remove-Item -Recurse -Force "$env:APPDATA\Antigravity" -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Antigravity" -ErrorAction SilentlyContinue

Optional logs
Remove-Item -Recurse -Force "$env:USERPROFILE\AppData\Local\Temp\Antigravity" -ErrorAction SilentlyContinue

macOS Terminal

# Quit Antigravity first
osascript -e 'tell application "Antigravity" to quit' 2>/dev/null || true

Remove app support and caches
rm -rf "$HOME/Library/Application Support/Antigravity"
rm -rf "$HOME/Library/Caches/Antigravity"

Linux Bash

# Kill the process if running
pkill -f Antigravity || true

Clear config and caches
rm -rf "$HOME/.config/Antigravity"
rm -rf "$HOME/.cache/Antigravity"

• Install the previous Antigravity installer that predates the Credits feature, then sign in and test a light prompt.

If you need a side by side comparison of subscription behavior across builds, see this follow up quota explainer. Step 4 If you are at zero for the week, wait for the weekly reset

• Note your account’s weekly reset day and time and plan heavier runs shortly after that window.
• Keep AI Credits off until you confirm normal consumption.

Alternative Fixes and Workarounds

Use a different project or workspace with its own quota

• If your organization uses project level pools, switch to a project with available quota.

Schedule heavy jobs right after the weekly reset

• Queue large tasks immediately after the reset to maximize the uninterrupted window.

Break up heavy tasks

• Split one large job into smaller runs across multiple days to stay under the weekly ceiling.

Switch models or tools that consume fewer credits

• Where configurable, pick smaller models or reduce tool calls to cut cost per request.

Troubleshooting Tips

• Confirm the Credits toggle actually stuck after restart. Some builds ly toggle but require relaunch to apply.
• Check the usage meter and reset schedule in your account page to verify you are not already at the weekly cap.
• Verify background automations are paused. Hidden workflows can deplete quota.
• Test with a trivial prompt. If even a trivial prompt fails, you are likely hard capped by the weekly pool and must wait or switch projects.
• If you reinstalled, make sure old config folders were removed before installing the prior build.

For common patterns that trigger limits sooner than expected, see this practical guide to quota triggers.

Best Practices

• Keep AI Credits off by default and enable only when absolutely necessary for a specific run.
• Maintain a performance budget per task and test prompts with a small dry run before scaling up.
• Schedule heavy workflows near the weekly reset and avoid running parallel jobs that multiply consumption.
• Document your organization’s quota pools and who owns them so unexpected drains can be traced quickly.
• Keep one stable build installed and archive a prior installer so you can revert without delay.

Final Thought

The lockouts are not a bug. They are a new weekly quota plus the AI Credits multiplier. Turn off Credits, run lighter prompts, or use a prior build, and you will get back to productive runs without surprise week long waits.