1.20.6. Currently iām using this version
1.20.6. Currently iām using this version
I was very happy that Google Launched Anti-gravity which is such a stable and competitive IDE. I tried recommending it to everyone but because of this new quota issue everyone moved back to cursor. And I myself moved back to Claude code. Very disappointed with Anti-gravity quota allocation because of which they will lose adoption of it.
Same here. The quota is being drained at an absurd rate! Yesterday, I asked for some CSS adjustments and my quota dropped by 1/5 in just a few minutes of use. It wasnāt even anything heavy⦠just CSS tweaks that ChatGPT does for free in seconds. The refresh was scheduled for a little over 4 hours last night. This morning, it changed to 5 days and 5 hours, and the usage remained the same as yesterdayāmeaning it wasnāt renewed.
On top of that, my credits were consumed even though I hadnāt hit the quota limit. And again, at an outrageous rate for very trivial tasks. At work, we are testing several models; this week it was CODEX. I managed to work the entire week without any quota issues using the same type of prompts.
I pay for the AI Pro plan, but I feel like Iām being cheated. Itās not worth it.
even githubcopilot is seems better has way more quota for opus as well with just 10 $
Just did a test. I wrote a MD file with 27 lines containing the requirements for creating a simple breadcrumb component. I provided the interface and a list with 7 properties for this componentāvery direct and succinct. It didnāt even code anything; it just wrote the Implementation Plan for approval. Boom, 1/5 of my quota is gone. This is absurd. I spent the whole week working with Codex and I still have 70% of my quota for the week and 100% for the day. If I want to implement the breadcrumb and another component, my quota will vanish in minutes, and Iāll have to wait until Wednesday for it to refresh. Ridiculous.
Am I the only one with the problem where the agent ask for authentication. Where do I even authenticate I am already logged in to my acc
Yeah, this is exactly the problem.
A simple task like writing an implementation plan shouldnāt consume that much quota. But right now even small, basic prompts are draining a huge percentage.
Iāve seen similar reports where people lose quota after just 1ā2 prompts, or even without using it much.
This makes it almost impossible to use Antigravity for actual development work.
At this point itās not even about ārate limitsā ā itās about unpredictability.
You donāt know:
- how much a task will cost
- why it consumed so much
- how to avoid it next time
Thatās the real issue.
Until thereās transparency or some kind of usage breakdown, even simple workflows like building components become risky.
Youāre not the only one.
Iāve faced this too ā it keeps asking for authentication even though Iām already logged in.
Thereās no clear place to re-authenticate either, which makes it even more confusing.
Feels like the session/token is not syncing properly on the backend.
Right now the only temporary workaround I found is:
- restart the session
- or reload / re-login
But even that doesnāt always fix it permanently.
Definitely another issue that needs attention.
This actually makes a lot of sense.
Iāve been suspecting the same ā this doesnāt feel like a bug anymore, it feels like a shift in how the system works.
The behavior weāre seeing:
quota draining very fast
āexhaustedā showing even for small tasks
authentication prompts
inconsistent resets
ā¦all point towards a backend change rather than random issues.
If Antigravity is moving towards a credit-based system, then the main problem right now is lack of transparency.
Because users still think in terms of:
5-hour reset
fixed quota
But internally it seems like:
credits are being consumed dynamically
different actions have different costs
Thatās why everything feels unpredictable.
I think this would be much less frustrating if Google clearly showed:
how many credits a task uses
remaining credits
why something is marked as āexhaustedā
Right now it just feels like quota is disappearing without explanation.
