Skip to main content
RESETGEMINI
QUOTA TELEMETRY // v2.6
中文
MODULE 03 // AGENTIC_IDE_QUOTA

Google Antigravity Quota: 5-Hour Sprint vs. Weekly Hard Cap

Solve the notorious "5-hour vs 5-day trap": learn how Antigravity pairs short rolling sprint refills with an underlying weekly hard cap, and stop autonomous agent loops from burning your week.

⚡ THE 5-HOUR VS 5-DAY LOCKOUT TRAP EXPLAINED

Paid tiers (such as Google AI Pro) promote fast 5-hour rolling refreshes inside Antigravity. However, Google enforces an underlying 7-day weekly baseline cap beneath those sprint windows. If an intensive refactor, full-repo scan, or stuck retry loop burns your remaining weekly baseline inside one afternoon, the UI stops offering 5-hour resets and jumps straight to a 4–7 day lockout until your weekly cycle refreshes.

✓ Normal Sprint Consumption
Depletes active 5h slice only
Weekly baseline remains healthy -> unlocks in <= 5 hours
⚠ Runaway Agent Loop / Unpruned Repo
Saturates 5h slice rapidly
Exhausts entire weekly baseline -> triggers 4–7 day multi-day lock

4 Proven Tactics to Avoid a Multi-Day Antigravity Lockout

GUARD-01

Monitor Baseline Before Big Refactors (/usage)

Run /usage or /quota inside the CLI/panel before launching multi-file autonomous tasks so you never unknowingly cross the weekly threshold.

GUARD-02

Add a Strict .antigravityignore File

Prevent context indexing from repeatedly ingesting node_modules, dist, .git, lockfiles, and binary assets on every agent step.

GUARD-03

Switch to Fast Mode / Gemini Flash for Routine Edits

Reserve heavyweight Pro/Ultra reasoning models for architecture and debugging; keep CSS tweaks, boilerplate, and small fixes on Fast Mode.

GUARD-04

Abort Failing Retry Loops Immediately

If an agent repeatedly fails the same test or build error 2–3 times in a row, cancel the run manually and inspect the error yourself — infinite retry loops are the #1 cause of weekly burnouts.

Recommended .antigravityignore Starter Templategitignore
# Dependencies & build artifacts
node_modules/
dist/
build/
.next/
.astro/
coverage/

# Version control & caches
.git/
*.log
*.lock
package-lock.json
pnpm-lock.yaml

# Large media & binary dumps
*.png
*.jpg
*.mp4
*.zip
*.sqlite
[02] WINDOW_CALC // PERSONAL_RECOVERY_ESTIMATOR.ICS // GCAL // URL_SYNC

Rolling Window & Lockout Recovery Calculator

Estimate when your 5-hour Gemini App / Antigravity window or 7-day weekly cap unlocks, or convert a CLI/UI remaining countdown into your exact local timestamp.

WINDOW PROFILE
ESTIMATED RECOVERY TELEMETRY
ESTIMATED LOCAL UNLOCK
--
TIME REMAINING
--:--:--
↗ Google Calendar
[05] FAQ_LOG // HIGH_FREQUENCY_DIAGNOSTICS

Frequently Asked Questions

[01]Is the 5-day Antigravity lockout a bug?+
Usually no — it means your cumulative compute usage hit the underlying weekly baseline cap rather than just the 5-hour rolling window. Once the weekly ceiling is exhausted, 5-hour intervals stop replenishing until the weekly anchor resets.
[02]Can I still work if Antigravity locks my Pro model quota?+
Yes: switch to Fast Mode / lighter Flash models if available, check whether Gemini CLI with an independent GEMINI_API_KEY bucket meets your immediate need, and prune your workspace with .antigravityignore before your next reset.