REPORT BUG - Excessive 7-10 day lockouts in Google Antigravity (AI Pro) after minimal usage

Report date: February 15, 2026
Affected plan: Google One AI Pro (2TB) + Antigravity IDE
Affected model: Claude Opus 4.6 (primarily)

Problem description

I’m a developer using Antigravity IDE to build a complete web hosting system (similar to SiteGround Pro infrastructure) with proprietary DNS server, zone management, email server, and multiple custom functionalities. Antigravity is essential for my workflow because:

  • Direct SSH access to my VPS for live development

  • Real-time server file editing and debugging

  • Claude Opus 4.6 for complex system architecture assistance

  • Integrated environment for production server management

The critical issue: After just 2-3 development requests to Claude Opus model, I receive 7-10 day complete lockouts instead of the 5-hour refresh windows advertised by Google. This makes professional development work completely impossible.

Specific lockout behavior

  • Request 1-2: Normal development queries (nginx configuration, DNS zone setup, etc.)

  • Request 3: System locks with “model quota exceeded”

  • Lockout duration: 7-10 days (not 5 hours as advertised)

  • After lockout ends: First request triggers immediate new 7-10 day lockout

  • Pattern: Infinite loop of week-long lockouts after minimal usage

This is not heavy usage. These are standard development tasks:

  • Reviewing configuration files

  • Debugging DNS zone syntax

  • Assistance with mail server setup

  • Code review for security best practices

Critical discrepancies

  1. Advertised vs. Reality:

    • Advertised: “Generous quotas with 5-hour refresh windows”

    • Reality: 7-10 day lockouts after 2-3 requests

  2. Quota monitor inaccuracy:

    • Monitor shows 70-80% quota remaining

    • IDE blocks requests with “quota exceeded” error

    • No correlation between displayed quota and actual availability

  3. Disproportionate consumption:

    • Simple requests consume massive quota unpredictably

    • No transparency on what counts toward limits

    • Impossible to plan or optimize usage

  4. Infinite lockout loop:

    • Wait 7-10 days for unlock

    • Make ONE request

    • Immediate 7-10 day lockout again

    • Makes the service completely unusable

Pattern observed in community

This is NOT an isolated case. Multiple developers report:

  • January 2026: Timers changed from hours to days without announcement

  • Version 1.15.6 (Jan 23): Worsened lockout behavior significantly

  • Claude models specifically affected: Disproportionate restrictions vs. Gemini models

  • Same quota monitor bugs: Shows availability but blocks requests

  • Professional work disrupted: Real projects halted by arbitrary lockouts

Source references: Google AI Developers Forum, Antigravity GitHub discussions, multiple Reddit threads (r/GoogleAI)

Business impact

  • Production project halted: Cannot complete paid client work

  • Financial loss: Paying monthly for unusable service

  • No viable workaround:

    • Claude.ai lacks VPS/SSH access needed for server development

    • Other IDEs don’t offer Claude Opus 4.6

    • Gemini models insufficient for complex system architecture tasks

  • Forced migration consideration: Evaluating Cursor IDE, Windsurf despite preference for Antigravity

I am a paying customer who cannot use the service I’m paying for.

What makes this suspicious

  1. Timing: Lockout severity increased after Gemini 3 launch

  2. Model discrimination: Claude models lockout aggressively; Gemini works normally

  3. Lack of transparency: No official acknowledgment or communication

  4. Infinite loops: Suggests systematic policy rather than technical bug

If this is policy to favor Gemini: Communicate it clearly. Don’t advertise “5-hour refresh” while delivering “7-10 day lockouts.”

If this is a bug: It’s critical priority - paying customers cannot work.

Requested action

As a paying Google One AI Pro customer, I formally request:

  1. Immediate investigation of lockout timer bugs (5 hours → 7-10 days)

  2. Transparency on actual quota limits and consumption metrics

  3. Fix for infinite lockout loops (unlock → immediate re-lock)

  4. Quota monitor accuracy (display should match actual availability)

  5. Official communication about any policy changes affecting third-party models

  6. Compensation or refund for service period where advertised functionality was unavailable

Technical environment

  • Plan: Google One AI Pro (2TB storage tier)

  • IDE: Antigravity latest version (as of Feb 15, 2026)

  • Primary model: Claude Opus 4.6

  • Use case: Professional server infrastructure development

This report represents legitimate professional usage by a paying customer. The service is marketed for development work but currently cannot support even minimal development activity.

9 Likes

Same position. Nicely put.

same thing happens. this happens since Google put opus 4.6 on the IDE. never happened before when using opus 4.5. this should be Google first priority

1 Like

This problem already appeared way before opus 4.6, somewhere around version 1.14.2

1 Like

How can i raise a ticket / bug report for myself? I have the same :

You have reached the quota limit for Claude Sonnet 4.5. You can resume using this model at 2/20/2026, 5:15:31 PM. You can upgrade to the Google AI Ultra plan to receive the highest rate limits.

Antigravity Team suggest using the built in Provide Feedback page in Antigravity settings as the issues reported there goes straight to the Dev.

Im in the same boat. This is the first time I’m seeing 7-day locks

I am experiencing this exact same issue. I’ve been stuck in this “quota exceeded” lockout loop for over a month. Initially, I thought it was normal, but I recently realized my Gemini 3 Pro quota hits 0% instantly even with extremely minimal or zero usage in Antigravity.

Same issue here. Please let me know if someone got a fix.