Feedback on Antigravity’s Token & Quota Policy (From a Pro User Perspective)

Google Antigravity
1

I’d like to share a recent experience and a broader concern regarding Antigravity’s current quota behavior.

After submitting a single prompt using Claude Opus, my entire daily quota was consumed instantly. Previously, Pro users had a more flexible quota model (roughly 3–5 hours of effective usage). At this point, it appears that the system effectively behaves as “one prompt equals one full day of quota.”

This creates serious friction for Pro users because it:

  • Makes Claude Opus and Claude Sonnet practically unusable despite being paid features

  • Breaks real-world development workflows that rely on iteration and refinement

  • Conflicts directly with the expectations associated with a Pro subscription

Free vs. Pro User Balance

For free accounts:

  • Early limitations and purchase prompts are understandable and even healthy for conversion.

However, applying a similar level of restriction to Pro users significantly degrades the experience. A paying user should not:

  • Be unable to predict quota consumption

  • Risk losing an entire day of usage with a single prompt

This unpredictability directly undermines trust in the product.

What Actually Differentiates Antigravity?

When compared to competitors:

  • Most IDEs now offer very similar functionality

  • Antigravity’s real differentiator was its quota-based, developer-friendly usage model

With the current behavior, this advantage is effectively lost.

Connection to Recent Technical Issues

Recently, there have been ongoing issues such as:

  • .md file tracking problems

  • Repeated “Please try again” errors

It appears that in response:

  • Free users have been subjected to heavier restrictions

  • Pro users have had their quota “duration” extended

In practice, however, this results in less usable capacity for Pro users, not more.

Constructive Suggestions

To avoid losing the existing user base, the following changes would be extremely valuable:

  1. Clear quota definitions for Pro users

    • e.g., maximum consumption per prompt

  2. Separate, visible quotas for Claude Opus and Claude Sonnet

  3. Prompt-level quota consumption previews

  4. A protected iteration space for Pro users

    • Allowing safe multi-step experimentation

  5. Soft limiting instead of hard cutoffs

    • Throttling rather than full-day exhaustion for premium models

Conclusion

Antigravity already has a knowledgeable and invested user base. What this base expects is:

  • Transparency

  • Predictability

  • A Pro tier that actually feels “Pro”

The current quota behavior unintentionally conflicts with these expectations. I hope this feedback is taken into account and that the Pro user experience—especially for Claude Opus and Sonnet—will be reconsidered.

Respectfully.

1 Like