A Brief Discussion on Google's Strategic Shift Following the Google AI Pro Quota Reduction
I originally intended to write a post to vent about the Antigravity quota reduction a day or two after it happened, but I was busy with other things over the weekend. By the time I wanted to start writing this week, it felt like too much time had passed, and writing about it now might seem like I'm just chasing trends. However, after experiencing a situation where I couldn't use the Claude model despite having remaining quota, and seeing some new information trickling in, I decided it was worth organizing my thoughts.
The Incident
On March 12, many users opened Antigravity in the morning only to find their Gemini Pro/Claude model quotas had dropped to 0, despite having plenty of quota the day before. Looking at the reset time, it appeared that a rolling weekly quota limit had been triggered. At the time, the community was debating whether this was a bug or if Google was further tightening quotas.
To be fair, everyone somewhat expected a tightening of quotas. After all, the previous "burn rate"—with 5-hour cooldowns, separate quotas for each family account, and different quotas for different services—was clearly unsustainable. Everyone was just making the most of it while it lasted. Furthermore, with the "buy a phone, get a half-year subscription" promotion in the second half of last year, and the half-price annual Pro subscription offer at the end of the year, the user base grew significantly, making subsequent tightening inevitable. Therefore, when the rolling weekly quota for the Claude model was introduced in late January, most people found it reasonable and didn't react strongly (or so I thought).
However, this latest round of limits was unexpected. Other providers at the $20 tier do not restrict high-end model usage to this extent.
In fact, signs of deteriorating experience appeared even before the March reduction. Starting in February, some users reported that Gemini felt "dumber," suspecting that the model had been quantized or that resources had been scaled back. At the time, I replied that I didn't feel much difference, but by mid-February, I started to notice something was wrong. Antigravity tasks would run for a long time without being completed properly. Initially, I suspected I hadn't explained things clearly, or that some steps were inherently complex and beyond its capabilities.
It wasn't just the model quality that was declining; the rate of quota consumption also accelerated significantly. Sometimes, the Claude model would burn through the 5-hour quota in just 2–3 tasks. After burning through two such cycles, the weekly quota would be down to 60%. In other words, users were facing a double blow: "weaker models" and "less quota."
Following the reduction, Google released a statement clarifying the positioning of each plan:
We're evolving Google AI plans to give you more control over how you build. Every subscription includes built-in AI credits, which can now be used for Antigravity, giving you a seamless path to scale.
Google AI Pro is the home for the practical builder, hobbyists, students, and developers who live in the IDE and don't necessarily rely on an agent. This plan features generous limits for Gemini Flash, with a baseline quota included to "taste test" our most advanced premium models.
Google AI Ultra serves as the daily driver for those shipping at the highest scale who need consistent, high-volume access to our most complex models.
If you're on Pro but need "extra juice" for a heavy sprint or deeper access to premium models, simply top up your AI credits to customize your plan.
Keep building. Keep shipping.
In short: The Pro plan is positioned with Gemini Flash as the primary model, while advanced models (Gemini Pro, Claude) are intended only for "taste testing." Ultra is the plan for those who need to use advanced models extensively. If Pro users temporarily need more quota, they can purchase additional AI Credits to top up.
About AI Credits
I don't have an issue with using AI Credits to top up model quotas. After all, the 1,000 credits provided monthly were originally intended for image and video generation in Google Lab, but without a clear concept or need, I didn't know what to generate. Being able to use them to supplement model quotas is actually more practical.
It is worth noting that on the same day as the quota reduction, Google published How we're reimagining Maps with Gemini, announcing the integration of Gemini into Google Maps with conversational search ("Ask Maps") and the most significant visual upgrade to navigation in a decade, "Immersive Navigation," launching first in the US and India. Compressing quotas for developer tools while pouring AI capabilities into consumer products—when these two things are viewed together, the strategic direction becomes clear.
On March 18, Ryan J. Salva, Senior Director of Product for Google Code Assist, explained in Service update: mitigating abuse and prioritizing traffic #22970 that free users of Gemini CLI can only use Gemini Flash, while Pro and higher tiers can use Gemini Pro. Traffic priority is determined based on account status and license type, with paid users prioritized and free users throttled. I suspect this was primarily targeted at those who previously registered massive numbers of accounts for use with OpenClaw.
On the same day, my Antigravity Claude model was completely unusable despite having a full quota, stuck in a loop of "Working" and "Generating" messages. It seems it wasn't just a model quota issue; the server resources allocated to the models might have also been reduced.
On March 19, Google AI Studio announced the "Build" feature. I found a more comprehensive application in this article: AI Studio officially supports full-stack development! Google launches Vibe Coding, letting you build frontends and Firebase with just your voice. It allows users to create a website including a Cloud Firestore database and OAuth functionality using commands. However, one should verify the billing status of Firestore on GCP to avoid unexpected charges.
Taken together, these moves point to a single trend: Google is reallocating AI resources from standalone developer tools (Antigravity, Gemini CLI) to integrated applications within its own ecosystem (Maps, AI Studio Build). For Google, making AI a built-in capability of its own products has more strategic value than maintaining a high-quota third-party developer tool. The strategic focus is shifting from developer users on the consumer side to a "use-as-you-go" developer system centered on ecosystem integration.
Is it still worth subscribing to Google AI Pro?
| Feature | Plus | Pro | Ultra |
|---|---|---|---|
| AI Credits (Shared Pool) | 200 / mo | 1,000 / mo | 25,000 / mo |
| AI Assistant | |||
| Gemini 3.1 Pro | ✓ | ✓ | ✓ |
| Deep Research | ✓ | ✓ | ✓ |
| Deep Think Reasoning Model | — | — | ✓ |
| Gemini Agent | — | — | ✓ (US only, English only) |
| Google Search AI Mode (Gemini 3 Pro) | ✓ | ✓ | ✓ |
| Search Labs Experimental Features | ✓ | ✓ | ✓ |
| AI Phone Calls | — | ✓ (US only) | ✓ (US only) |
| Use Gemini directly in Google Apps | ✓ | ✓ | ✓ |
| Creative Generation | |||
| Video Generation | Veo 3.1 Fast | Veo 3.1 Fast | Veo 3 |
| Photo to Video | ✓ | ✓ | ✓ |
| Google Photos Magic Editor | — | ✓ (US only) | ✓ (US only) |
| Image Generation (Nano Banana Pro) | ✓ | ✓ | ✓ |
| Flow Video Creation | ✓ | ✓ | ✓ |
| Lyria 3 Music Generation | ✓ | ✓ | ✓ |
| Learning Tools | |||
| Multi-page Reports | ✓ | ✓ | ✓ |
| NotebookLM | ✓ | ✓ | Strongest Model |
| Programming | |||
| Jules Async Programming Agent | — | ✓ | ✓ |
| Gemini CLI / Code Assist IDE | — | ✓ | ✓ |
| Google Antigravity Agent Model | — | ✓ | ✓ |
| GCP Credits (Google Developer Program) | — | US$10 / mo | US$100 / mo |
| Additional Services | |||
| Cloud Storage | 200 GB | 2 TB | 30 TB |
| Family Group Sharing | Up to 5 | Up to 5 | Up to 5 |
| Google Home Premium | — | ✓ | — |
| YouTube Premium | — | — | ✓ |
Comparing the table, the main difference between Plus and Pro lies in the programming features. I'll skip Ultra for now; the Gemini model's strength in programming is primarily UI design, and it doesn't stand out in other aspects compared to Claude or ChatGPT. It's unlikely anyone would subscribe to this tier just for coding, especially with an additional $50 cost (the top tiers of the other two are $200, with Claude Max having an entry tier of $100).
So the question returns to: Is the extra programming functionality in Pro worth the price difference over Plus? If you only use an Agent to assist with development and don't use it to work on side projects after hours, the $20 plans from any provider are generally sufficient. But if you want to make Vibe Coding your primary development method, the quota requirements are completely different. The $20 plans from any provider are insufficient for continuous use. Antigravity used to barely manage this by switching between multiple accounts, but that was before the January quota limits.
After the March 12 adjustment, it's a different story. On one hand, the Gemini Pro and Claude model quotas in Google Pro are already lower than comparable plans from other providers; on the other hand, the aforementioned issues with declining model quality and service instability have not improved. With lower quotas, poorer quality, and insufficient stability, it's really better to switch to another provider at the same price point. Over the past half-month, I've heard of people switching to Claude Code or ChatGPT Codex.
Unless Google makes significant adjustments to its plans later, I wouldn't recommend subscribing to Pro under the current circumstances. For non-programming ecosystem users, Plus and Pro are identical in usage; for programming, Pro is currently too lackluster. If you need it, you're better off subscribing elsewhere. In fact, over the last two weeks, the Gemini App has been constantly prompting me to upgrade to Ultra, which makes Pro feel like an awkward existence even for Google itself.
Change Log
- 2026-03-20 Initial version created.