GOAL
The goal is to gather useful information, identify common patterns, and provide constructive feedback to Google while requesting greater transparency and clearer information regarding quota limits, usage calculations, and how quotas are enforced.
WHY THIS MATTERS
Developers rely on tools like this for their daily work. When quotas are exhausted unexpectedly, workflows can stop without warning, making it difficult to plan projects, estimate costs, or understand how usage is being calculated.
The purpose of this thread is to collect user experiences in one place and determine whether there are common patterns affecting multiple users.
REPORTING GUIDELINES
Please do not post if you are using the Free plan![]()
Free plans are expected to have significantly lower quotas, which makes comparisons less meaningful for this discussion and are unreliable.
If you are experiencing this issue, please share:
- A screenshot of your quota page. (example)
- Your IDE details (
Help → About).
Antigravity IDE Version: 2.0.4
VSCode OSS Version: 1.107.0 (user setup)
Commit: def9583aef9852ff94cb0dea16ede9bb6b095b30
Date: 2026-06-02T00:22:56.234Z
Electron: 39.2.3
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200
Language Server CL: 924974766
-
The subscription tier you are using.
(pro / ultra / cloud key) -
Which model you were using most frequently.
-
Whether the quota exhaustion matched your expected usage or past experience.
-
Any additional observations that may help identify patterns.
(like RAG, uploaded docs, subagents, parallel execution, . . .)
DONT :
“Im also having issues“
“yeah, limits are a joke“
**this does not help, I will delete these comments (If I can).**
.
JUST TO CLARIFY: I am not a Google employee and have no affiliation with the company. I just received a mention (@) requesting an update on a issue.

