Google Antigravity issues

Google Antigravity
1

Dear Google AI Support Team,

I am writing to report critical issues with my Google AI Pro subscription and Antigravity IDE that are completely breaking my workflow. I am facing a severe quota management bug, persistent authentication loops, random application crashes, and context failures, all of which are preventing me from using the premium service I am paying for.

Account Details:

  • Subscription: Google AI Pro (Active through March)

Problem Description: I am experiencing a massive 140-hour quota lockout in Antigravity, which directly contradicts the advertised 5-hour refresh cycle for Pro subscribers. Additionally, the application’s basic login functionality is failing, the IDE frequently crashes or loses context, and it fails to consistently read repository configurations. The service worked fine for the first two days, but from the third day onward, these frustrating bugs have made my Pro subscription feel like a huge mistake.

What I Was Doing When Locked: I opened Antigravity, and the UI falsely displayed my quota as 100% available. I submitted a single, small input to the Gemini Pro model. Instantly, the system hit the total quota limit and locked me out, displaying a 140-hour wait time to refresh. I even tested this on a friend’s Pro account to verify—it also showed 100% available, accepted one small prompt, and instantly locked them out for 140 hours.

Expected Behavior: As a Google AI Pro subscriber, I should experience:

  • Accurate quota UI that displays my true limits, not a false 100%.

  • A maximum wait time of 5 hours for my quota to refresh.

  • A seamless, successful login on the first attempt when opening the IDE.

  • Stable generation without sudden crashes or context corruption.

  • Automatic and consistent utilization of custom skills and guidelines configured in the repository’s .agent file.

Actual Behavior:

  • Severe Quota Lockout: A 140-hour (nearly 6 days) lockout period triggered immediately after a small prompt.

  • Authentication Loop: I am required to go through a 3-attempt login loop just to get into the app (Open → Login fails → Close → Reopen → Login fails → Close → Reopen → Login successful on the 3rd try).

  • Sudden Errors & Forced Restarts: The IDE frequently stops mid-generation with a generic “error occurs” message. I cannot simply continue; I am forced to completely close and reopen Antigravity to resume work.

  • Context Collapse & False Outputs: Sometimes, if an error occurs and I am able to click “continue,” the agent’s previous context, thinking, and data completely collapse. This causes the system to crash momentarily, recover, and then generate completely false outputs based on broken context.

  • Inconsistent .agent Parsing: I have configured custom skills and guidelines in the .agent file. While the agent occasionally picks these up automatically, most of the time it ignores them entirely. I have to constantly manually instruct the agent to use these established skills, defeating the purpose of repo-level configuration.

Troubleshooting Steps Already Taken:

  • Verified my Google AI Pro subscription is fully active.

  • Tested and replicated the exact same false-100% quota bug on a second Pro account.

  • Attempted to restart the IDE to bypass sudden errors, which only sometimes works but often results in corrupted context.

Impact: This issue is incredibly frustrating and makes the Pro subscription unusable for its intended purpose. I upgraded specifically for the 5-hour refresh cycles, but going from an advertised 5 hours to a 114-240 hour lockout over a simple input is unacceptable. Furthermore, struggling to simply log into the application, constantly having to manually remind the agent of its configured skills, and losing my generation context to sudden crashes completely destroys my development flow and wastes even more time.

Request:

  • Please investigate the synchronization bug causing the 140-hour lockouts and the false 100% UI display.

  • Reset my quota immediately and ensure my account correctly follows the 5-hour refresh schedule.

  • Investigate and patch the caching issue causing the 3-attempt login loop.

  • Address the stability issues causing sudden “error occurs” halts and the subsequent context collapse.

  • Fix the .agent configuration parsing so the agent reliably and automatically utilizes repository-level skills without requiring manual prompting every time.

1 Like