Honestly, Google Antigravity has been unusable for almost a week. My subscription is about to expire, and I am getting suspended every three or four days due to rate limits. How is this supposed to be used properly?
Due to the frequent and long-lasting interruptions, I have become very cautious in using my models. Today, after using it for a short period of time, I went online for a while, then came back to continue using it, and suddenly I found a message in the chat telling me that the renewal of the limit will be on the 28th, i.e. after four days, even without using it.
Hello @abu_bakr,
We appreciate your honest feedback and are very sorry to hear about the persistent issues you’ve encountered this past week. This is certainly not the standard of reliability we strive for with Antigravity. Your report has been logged and will be shared internally.
Same issue here. Maybe 10 minutes of use. Then waiting days for model usage (opus, sonnet), and with gemini pro have all of a sudden gotten out of quota for a whole day. Pro user
Also since last update it has been that unstable I have had to resort to using codex aswel, they really need to fix the editing code the agents using as it breaks my django templates and css every bloody time I use a gemini model for any frontend work.
I hit the rate limit but typically it’s only a few hours I need to wait to get back. I’m only using this to test the potential so no deep work pushing it. Today in then said I used the rate limit and need to wait 7 days to resume. I’m quite surprised that the wait time has increased so drastically.
I haven’t been able to use Antigravity properly for the past three weeks. When are you planning to fix the bugs with an update and reset the Claude refresh time for all users???
As mentioned on another post - same story here. Was great with a few quirks, for the past 5-6 weeks, it’s been slow, unreliable and hangs to the point that I have to restart frequently just to get the agents unstuck.
I’m on ultra plan. I started getting this since last night. I thought it was for one corrupted chat as I tried new chat session and it worked again. But today, I am getting twice in a row with different chat. Cached mem is around 511MB. What is the issue? And I asked the agent to retrieve the context from the corrupted chat and it said it couldn’t find it. My work is lost as I keep creating new chats and it gets corrupted. Is it due to how I use the skills or workflow? Or it is just something at backend?
