The Zero-Quota Trap in Google Antigravity: How I Built an Autonomous Multi-Account Skill

Description and use

Antigravity Autopilot continuously monitors true quota, automatically switches accounts when the active one is depleted, restarts the IDE, and notifies the user, eliminating manual quota management.

Problem

Unexpected quota limits (HTTP 429) interrupt developer workflow in Google Antigravity, requiring manual account switching and IDE restarts.

Outcome

Within 60 seconds of quota exhaustion, the controller automatically switched to a healthy account, relaunched the IDE, and notified the user, restoring uninterrupted development.

Workflow

• 1. Install Autopilot via git clone and install script.
• 2. Configure as an Agent Skill or for Gemini CLI.
• 3. Autopilot runs a 60‑second watcher that polls Google Quota API.
• 4. Calculates True Quota = min(5h_bucket, weekly_bucket).
• 5. If active IDE account True Quota <= 2.0%, selects the Pro account with highest True Quota.
• 6. Gracefully restarts Antigravity IDE and injects new credentials via API.
• 7. Sends macOS notification to user.
• 8. 5‑minute watchdog auto‑heals daemons and triggers rolling window refreshes.

Evidence

During live testing, the active account najeepyasir dropped to 0.2% quota. Within 60 seconds, the controller identified the exhaustion, disqualified depleted accounts, verified that standby account yasir.najeeb.official had reset to 70.6%, executed the credential injection, relaunched the IDE, and notified the desktop.

Source

The skill is fully open source under the MIT license on GitHub and adheres to the open Agent Skills specification.

Source