Just tried out Antigravity 2.0. It’s a great platform, and I am really looking forward to the future models and the overall ecosystem you are building here.
I am writing to suggest a minor improvement regarding the quota limit display. Since the weekly rate limit was introduced for Pro and Ultra subscribers, I’ve noticed that the current display—which relies on a single progress bar—can be somewhat misleading.
Currently, when the weekly quota drops below a certain threshold (e.g., with 80% remaining), the UI switches from displaying the 5-hour window countdown to displaying the weekly countdown (e.g., “80% remaining • Refreshes in 6 days”).
This transition often leads to a common misunderstanding. We frequently see users complaining that they “hit the weekly limit after using just two 5-hour windows.”
However, if using two 5-hour windows only consumes 20% of the weekly quota, it actually means the total weekly allowance is very generous—equivalent to roughly 10 full 5-hour windows, which is highly competitive compared to other tools.
The core issue is that visualizing both the 5-hour short-term limit and the 7-day long-term limit on a single progress bar subconsciously makes users feel as though both quotas deplete at the same speed. When the display suddenly shifts to a weekly countdown, it creates unnecessary frustration and anxiety, making the limit feel much tighter than it actually is.
Suggested Solution:
Would it be possible to separate these two limits into distinct visual indicators? For example:
-
A primary bar/indicator for the immediate 5-hour window.
-
A smaller, separate indicator (or a simple text line) showing the remaining weekly allowance.
This would make it much clearer to users that they still have plenty of weekly quota left, even if they are currently waiting for a 5-hour refresh.
Thank you for your time and for continuously improving this platform!
Yeah, but the problem is, google realy want you to know that ?
“This would make it much clearer to users that they still have plenty of weekly quota left”
I think is on pourpose so you can´t know exactly that.
You should be aware that as recently as February, Pro plan subscribers had a 5-hour limit, and after the reset it was 5 hours again, not 7 days 
Google is introducing restrictions month by month.
They are introducing weekly limits like months ago, and this is reasonable.
Both Codex and Claude Code have it. This is nothing to be blamed.
However, bad displaying strategy really frustruates the users!
In my opinion, this change is unfair. And now, on top of that, the Flash 3 model has been removed, which used to be unlimited in the Pro plan. Now you’ll use up your quota regardless of whether you’re dealing with a simple or a complex problem.
Let’s see if you find it reasonable when they cut it more and more.
To think they’ll hear a suggestion that’s good for the consumer.
I think the weekly limit would be fair if we still had flash 3.1. Since the change yesterday 3.5 eats the allowance so quickly I will be lucky to get a few hours per week. If it stays as bad as that I’m done.
What will we do with weekly indicator, when token cost is absolutely bonkers? 15-20 mins work, and 7 days lockout for pro users.
Maybe graphical example ?
You should practice reading and comprehension instead of being emotional and not reasonable. It seems that you haven’t read my post and just want to express your dissatisfaction with Google. You are spamming the Antigravity Section with your post and I don’t know if this is really beneficial for future development of Antigravity
Seems not the case for me.
Have been gone with 2 5-hour-limit window and it still hasn’t gone to weekly limit
I think it’s more important to be constructive instead of being emotional for them to hear really impressive and useful feedbacks instead of your emotional output, right?
Well said, brother (or sister).
The current limits are actually very generous, enough for a developer coding heavily with flash 3.5
The issue is communication, if they just communicate what they think of Antigravity 2, recent WSL issues and will display remaining limit in the IDE, I would be much more comfortable using the IDE
Agree. Constructive ideas are what matter the most
Maybe try to write down your feedbacks in the in-app feedback form
