Title: [BUG] Phantom Quota Drain / "Quota Exceeded" Lockout on Startup (Gemini 3.1 Pro via Jio Entitlement)

Google Antigravity
, ,
1

Environment:

  • IDE: Antigravity IDE

  • Model: Gemini 3.1 Pro (Planning/Thinking models)

  • Account Tier: Gemini Advanced/Pro (via Jio 18-month subscription offer)

  • Workspace Context: MERN stack SaaS application

Description: I am experiencing severe, unprompted rate-limiting and “Model Quota Exceeded” errors upon simply launching the Antigravity IDE. Despite having an active Pro subscription and zero manual prompts for the day, I am instantly locked out. It appears the IDE’s background agents are causing phantom token consumption on startup, or the Jio/Google entitlement handshake is failing and defaulting to free-tier limits.

Steps to Reproduce:

  1. Used the Gemini 3.1 Pro model (specifically the planning model) moderately for 2-3 prompts during the previous day.

  2. Reached a quota limit by the evening (which showed a reset time of 8:30 PM).

  3. Closed the IDE for the night.

  4. Opened the Antigravity IDE the following day.

  5. Instantly received a “Model Quota Exceeded” error without executing a single manual prompt or task.

Expected Behavior: Opening the IDE should not instantly trigger a quota lockout. The token allocation should accurately reflect the Gemini Advanced/Pro limits. Furthermore, background agents (like workspace context syncing for a standard MERN codebase) should not silently drain the entire token quota while the IDE is simply initializing.

Actual Behavior: The system is either incorrectly identifying my Jio-provisioned Pro account as a Free-tier account upon initialization, or a background reasoning loop from the previous session resumed on startup and drained the entire token allocation instantly.

Troubleshooting Attempted:

  • Verified the Jio Pro offer is actively linked to the account.

  • Observed highly inconsistent refresh timers over the last week (e.g., a Friday lockout resetting on Monday at 10:30 PM, then a subsequent lockout resetting at 8:30 PM the following day).

Request: Could the engineering team investigate how the Antigravity IDE handles background token usage upon startup? Additionally, please verify if the Jio API entitlement handshake drops intermittently, causing the IDE to fall back to strict free-tier limits.

1 Like