Google triples Gemini usage limits for Antigravity twice

Google changed how it meters usage for Gemini models after Google I/O 2026, introducing compute-based limits across the product suite, according to reporting by 9to5Google and AndroidHeadlines. 9to5Google reports that usage caps for Gemini inside Antigravity, Google's AI coding workspace, were raised twice within days of the new policy taking effect. 9to5Google quotes Varun Mohan, a Director at DeepMind working on Antigravity, saying users could hit their weekly quotas "after a couple work sessions," and reports that Google reset paid-plan weekly quotas for all users for a second time this week. AndroidHeadlines and KuCoin report that the team tripled rate limits for paid tiers and pushed an automated notification to affected users; KuCoin cites BlockBeats reporting that the team acknowledged early mistakes and committed to listening to community feedback.

Editorial analysis - technical context: Public reporting characterizes the move as a shift from counting discrete prompts to a compute-based metering approach that factors in request complexity, feature usage, and chat-history length, per AndroidHeadlines. In general industry practice, metering that charges for computation and context length increases effective cost for long-running developer sessions and multimodal workloads because resource consumption scales with model size, context window, and feature set. That pattern helps explain the rapid quota exhaustion users reported when long chat histories and heavy coding interactions were counted against limited weekly allocations.

Platform metering changes are a common flashpoint for developer communities because they directly affect cost predictability and workflows. The tripling of paid-tier limits and the quota resets reported by 9to5Google, AndroidHeadlines, and KuCoin reduce immediate friction for paying users, but public coverage shows the change triggered broad user backlash and urgent corrective action. For developer-facing AI products, the episode highlights how billing model changes can generate rapid operational feedback loops between users and engineering teams.

For practitioners and observers:

• •Track official communications from Google/Antigravity for precise, product-level documentation of compute billing metrics and the exact formulae used to convert request attributes into quota consumption.
• •Monitor developer forums and telemetry for recurring quick quota exhaustion, especially for long-lived sessions or heavy multimodal tasks that drive high compute.
• •Watch whether compute-based metering is extended unchanged to other Gemini surfaces; current reporting indicates the raised limits apply to Antigravity only and that other parts of the Gemini suite still have the new caps in place, per 9to5Google.

Editorial analysis: The incident underlines a broader pattern where platforms moving to compute-based billing must balance operational cost control with developer predictability. Teams deploying large-context or multimodal models commonly face the trade-off between accurate cost attribution and acceptable user experience; careful communication and staged rollouts reduce backlash risk.

9to5Google quotes Varun Mohan saying users could hit weekly limits "after a couple work sessions." AndroidHeadlines reports users received an automated message indicating paid-plan quotas were reset and increased by 3x. KuCoin cites BlockBeats reporting that the Antigravity team acknowledged mistakes and pledged to act on feedback.

What is not documented in the cited reporting is an engineering-level breakdown of the compute accounting formula or a formal Google-issued public policy document published alongside the I/O announcements. Reporting to date is based on company acknowledgements via team posts and user-reported notifications.

Overall, the coverage shows a rapid product-level response to developer pain following a shift to compute-based metering for Gemini inside Antigravity, with paid-tier limits tripled and weekly quotas reset after user complaints, according to 9to5Google, AndroidHeadlines, and KuCoin.