The Trick
Four Google accounts, one quota each, one click to rotate
A few days ago I published a post on switching between Claude Code accounts without logging out. My next idea was the Antigravity version of it. Then I read the terms, and this is the post I wrote instead.
Google Antigravity gives every Google account a free quota. Most people have more than one Google account. Put those two facts together and you get the trick that is going around: sign in to Antigravity with three or four Google accounts, and when one runs out, switch to the next.
Doing that by hand means signing out and back in every time, so a small ecosystem of tools has grown up to do it for you. Search GitHub and you will find a long list of Antigravity account switchers: VS Code extensions with a sidebar of accounts, desktop apps, CLI wrappers. Several show live quota bars for every account and the time until each one resets. Some notice the rate-limit error and offer to switch. The most automated ones switch without asking.
They are not shy about what they are for. Two separate repositories carry the same one-line description: "Switch between multiple Google accounts in Antigravity to bypass model rate limits." Another advertises "automated quota failover", and another "Seamless HTTP 429 Failover" across an account pool.
I was going to write the step-by-step guide. I am not going to, for reasons this post explains. Instead it covers the whole picture: why the quota exists, why every free AI tier ends up farmed like this, how providers fight back, how these switchers actually work inside, what they cost you in security, and how to use more than one account in a way that does not put your Google account at risk.
This is the account your email lives on
Antigravity uses your Google account. If a ban lands, it lands on the same identity as your Gmail, Drive and Photos. During Google's February 2026 ban wave, some affected users reported problems with other Google services as well. A free AI quota is a strange thing to risk that for.
Key takeaway
"The trick is easy, and the tools make it easier. Whether you should do it is a different question."
Why The Quota Exists
A free quota is a demo paid for by someone else
Every agent run in Antigravity costs Google real GPU time. The free tier exists so you can try the product, and the limits exist because that GPU time is shared by everyone using it.
Antigravity's own plans page sets out three tiers. The free plan gets "a meaningful quota, refreshed weekly." Google AI Pro gets "a high, generous quota, refreshed every five hours until the weekly limit is reached." Ultra gets the highest quota, also refreshed every five hours.
Quota is not counted in prompts. Antigravity says you get more prompts when your tasks are simple and fewer when the agent has to do complex work. So a single heavy agent session can use up a free account's week.
Two sentences on that page matter for this post. The first: "Usage limits for this service are subject to modification. These adjustments may be necessary to manage system capacity and maintain service stability." The second is what is missing: bring-your-own-key is not supported. You cannot pay a separate bill to get past the plan limits. Within Antigravity, the plan is the limit.
That is the bargain. Google pays for a taste of the product, and the weekly reset is what keeps the cost of that taste fixed per person. One person with four accounts is four people's share of that capacity, taken from the same pool everyone else is using.
Key takeaway
"The free quota is sized per person. Rotating accounts is not getting more from Google, it is taking capacity from the next user."
Every Free Tier Gets Farmed
It is not an Antigravity story. It happens every time.
Antigravity is the current example, but every AI coding tool with a generous free tier has gone through the same cycle. Each time it ends the same way: everyone, including people who never farmed anything, ends up with a smaller free tier.
Cursor: free trials, one machine, many accounts
Cursor's Pro trial was farmed by creating new accounts on the same computer. Cursor's answer was the error many developers have now seen: "Too many free trial accounts used on this machine." It is tied to the device, so signing in with yet another account does not help. Its forum also shows the side effect: people on shared company networks or VPNs blocked from a trial they never used.
Gemini API: a free tier cut sharply overnight
In early December 2025, developers on the Gemini API free tier started seeing 429 errors. Widely reported numbers put Gemini 2.5 Flash at about 20 free requests a day, down from about 250, with 2.5 Pro removed from the free tier. Google did not blame any single group, but the effect is the end of the cycle: the free tier became much smaller for everyone.
Antigravity: rotation, then paying users complain
In March 2026, a user on Google's own developer forum asked Google to limit multiple accounts by hardware ID. The post said accounts were being rotated to get past the weekly limit, and that "for normal users, normal use in anti-gravity is no longer possible." A Google moderator replied that they would file a feature request. When paying customers start asking for enforcement, enforcement usually follows.
The cycle
A generous free tier launches. Tools appear that multiply it. Usage outgrows capacity. The provider responds with some mix of smaller quotas, device or hardware checks, and bans. Everyone who arrives afterwards gets a smaller free tier and more friction, including people who only ever had one account.
Key takeaway
"Farming a free tier does not beat the provider. It speeds up the moment the free tier shrinks for everyone."
How Providers Fight Back
Bans, a form, and the second strike
Google has already shown how it enforces Antigravity terms. The case was not multi-account rotation but something close to it: third-party tools using people's Antigravity login to reach Google's backend. It is the clearest public evidence of what enforcement looks like.
February 2026: the OpenClaw ban wave
Paying subscribers, including AI Ultra subscribers, lost access.
- From mid-February 2026, Google suspended Antigravity access for users who were sending traffic through OpenClaw and similar third-party tools using their Antigravity login tokens.
- These were paying customers. Reports of the wave included subscribers on the top AI Ultra plan, at around $250 a month.
- Varun Mohan, who leads the product at Google DeepMind, said publicly that this usage had "tremendously degraded the quality of service for our users."
The reinstatement terms
From the official announcement on the Gemini CLI GitHub, February 27, 2026.
- The stated cause: "use of 3rd party tools or proxies to access Antigravity resources and quotas."
- To get back in, affected users fill in a Google Form, review the terms, and acknowledge "that bypassing system measures or circumventing usage limits is prohibited."
- Accounts are reinstated automatically, usually within a day or two.
- The line that matters: "If an account is flagged for a second violation of ToS, it will be permanently banned."
What this means for account rotation
No ban wave has been announced for switchers yet. The rules that would cover one already exist.
- The acknowledgement users had to sign says circumventing usage limits is prohibited. Rotating accounts when one hits its limit is, by its plain purpose, circumventing a usage limit.
- The most automated switchers work as local proxies that inject other accounts' tokens into your requests, which is close to the "3rd party tools or proxies" wording in the announcement.
- The detection signals are cheap to collect and already used elsewhere: several accounts on one device or IP, signed in one after another, each switching right after the previous one hits a 429.
- And the penalty lands on the Google account, with a second strike being permanent.
Key takeaway
"Google has already written the rule, built the enforcement process and used it on paying users. Rotation is waiting for its turn."
Inside A Switcher
Two designs, both built on stored login tokens
The engineering is genuinely interesting, and it is the same idea as my Claude Code account switcher: the app has one login slot, so you swap what is in it. What differs is how far the tools go.
Reading through the public repositories, the switchers fall into two designs. I am describing them at the architecture level only. There is no setup guide here.
Design 1: profile swapping. Antigravity keeps its login and settings in a user-data folder, and the CLI also keeps a login in the operating system's credential store. A profile swapper copies those into a folder per account. To switch, it copies the chosen account's files back into place and restarts Antigravity. The app never knows other accounts exist. The extra feature is a watcher: it reads Antigravity's logs for rate-limit messages and offers a switch as soon as one appears.
Design 2: a local proxy with an account pool. This one does not swap files at all. It runs a small HTTP proxy on your machine and points Antigravity's traffic at it. Every request passes through the proxy, which adds the active account's login token. When Google answers with HTTP 429, meaning that account's quota is gone, the proxy holds the response back, picks the next account from the pool, and replays the same request with the new token. One project keeps a 100 MB buffer for exactly that replay. A background job polls Google for each account's remaining quota so it can switch before a 429 even happens. To the user, the quota never runs out.
What both designs have in common is the point of this post. Each needs working login tokens for every account, sitting on your disk all the time. One stores them as plain files per profile. Another stores them in a local SQLite database. The profile swapper's README says it directly: "These files contain usable credential material; keep the profile directories private."
My Claude Code switcher swaps one login between accounts I use for different work, one at a time, and every account keeps its own limits. The proxy design is the opposite: its whole job is to make several accounts' limits look like one bigger limit. The engineering is similar. The purpose is not.
The two designs
Design 1: profile swap
Antigravity --reads--> user-data folder + saved login
^
switcher copies <account>/ back into place, restarts the app
Design 2: local proxy + account pool
Antigravity --> local proxy --(token A)--> Google
| <-- 429 quota exhausted
+----(token B, same request)--> Google
tokens for A, B, C, D stored on disk the whole timeKey takeaway
"Same engineering as a normal account switcher. The difference is whether it swaps between your purposes or merges limits."
What It Costs You
The risks are bigger than a lost quota
Leave the terms aside for a moment. Purely as software you install, these tools make a trade most people would not make if they looked at it.
Every account's login token is in one place on your disk.
Solution - A switcher with four accounts is four live Google login tokens in one known folder or database. Anything that can read your home directory, a malicious npm package, a compromised extension, or a worm like the one I wrote up earlier, now gets all four at once instead of one.
An extension update can change what it does with them.
Solution - Most of these switchers are small projects from individual authors, installed from extension marketplaces that auto-update. Today's honest version is safe only as long as every future update is honest too, and as long as the author's publishing account is never taken over. You are trusting that every time it updates.
A proxy sees everything you send.
Solution - The proxy design sits in the middle of every request, so it handles every prompt, every file you share with the agent, and every response. For personal projects that may be fine. For a company codebase, putting an unaudited third-party proxy between your code and Google is something your security team would want to know about.
A ban hits the Google account, not the tool.
Solution - Enforcement is applied to the Google accounts. The switcher is fine, your accounts are not. Under Google's published process, a second strike is a permanent ban, and that is an account that may also hold your email.
Linked accounts can be linked by the provider too.
Solution - Several accounts signed in one after another from the same machine and network is exactly the pattern device-level enforcement looks for. If the accounts are flagged together, they are likely to be acted on together, including your main one.
Key takeaway
"You are risking every Google account you add, plus every token on disk, to save the price of a subscription."
Doing It Properly
More than one account, without the risk
The test I use: why am I switching?
If I switch because the work changed, say office code to a personal side project, that is normal account use. If I switch because an account ran out, that is rotation, and it is what the terms are written to stop. That one question settles almost every case.
One account per purpose, not per quota
A company Workspace account for company code and a personal account for your own projects is a sensible split. It keeps company code away from your personal account, which your employer probably wants anyway. Switch with Antigravity's own sign-out (profile icon, bottom right, "Sign out from Google account") and sign in with the other account. It is slower than a one-click switcher, and that slowness is a good reminder of why you are switching.
If you keep hitting the limit, pay for the limit you need
Google AI Pro resets the quota every five hours instead of weekly. Ultra raises it further. Paid plans can also buy AI credits for overages, so a heavy week costs extra instead of risking a ban. If Antigravity is saving you hours of work, this is the cheapest version of the decision.
Use less quota per task
Antigravity charges complex agent runs more than simple ones. Smaller, well-scoped requests, a clear plan before the agent starts, and not asking it to rediscover a codebase every session all make the same quota go further. This works on every plan, including the free one.
Split work across tools, not across accounts
Using Antigravity for one kind of task, Claude Code or another tool for another, and a local model for simple autocomplete is entirely legitimate, and each tool keeps its own limits. If you want shared context across your own accounts on one tool, the Claude Code setup I wrote up does that without merging any limits.
Quick check before switching
Why am I switching accounts?
the project / employer changed -> fine, switch normally
this account hit its limit -> rotation; pay, wait, or use another tool
a tool switches for me on 429 -> rotation, automatedKey takeaway
"Switch accounts when your work changes, not when your quota does."
Quick Answers
Questions people ask about this
Short answers to the things that come up most about Antigravity accounts, quotas and switchers.
- Is it against the rules to switch Google accounts in Antigravity to get more quota?
- Rotating accounts because one ran out is exactly what Google's enforcement targets. When Google announced Antigravity ban reinstatements in February 2026, the reinstatement form asked users to acknowledge that "bypassing system measures or circumventing usage limits is prohibited." Antigravity's plans page also says usage limits can change to manage capacity. If the reason you are switching is that an account hit its limit, assume you are in the territory the terms are written for.
- Can I use a work account and a personal account in Antigravity?
- Using separate accounts for separate purposes, such as a company Workspace account for company code and a personal account for side projects, is ordinary account use. The line is the reason for switching: switching because the project changed is fine, switching because the quota ran out is rotation. Google has not published a clear statement on two paid accounts for one person; the forum answer people cite came from a community member, not from Google.
- How do Antigravity account switcher extensions work?
- There are two main designs. Profile swappers copy the app's user-data folder and saved credentials into a per-account folder, then copy the chosen one back and restart Antigravity. Proxy switchers run a local HTTP proxy between Antigravity and Google, keep a pool of account tokens, and when a request comes back with HTTP 429 they retry the same request with the next account's token. Both depend on having usable login tokens for every account stored on your disk.
- Are account switcher extensions safe?
- They hold working login tokens for every Google account you add, usually as files or a local database on disk. One project's README says it plainly: "These files contain usable credential material; keep the profile directories private." A proxy-based switcher also sees every prompt and every piece of code you send. A malicious or compromised update to any of these extensions would get all of that at once. Install one only if you have read its code, and remember a ban lands on the Google account, not on the extension.
- How do AI tools detect people farming free tiers?
- Publicly, the signals are device and network based. Cursor's "Too many free trial accounts used on this machine" error is triggered by trial history on the same device, and its forum shows it can also misfire on shared company VPNs and IP addresses. Google's February 2026 bans targeted traffic from third-party tools using Antigravity login tokens. Users on Google's forum have also asked for hardware-ID limits on multiple accounts, and a moderator said a feature request would be filed.
- What should I do instead when I keep hitting the Antigravity limit?
- Pick the option that pays for the capacity you actually use: Google AI Pro or Ultra raise the quota and reset it every five hours instead of weekly, and paid plans can buy AI credits for overages. Make each request count: smaller, well-scoped tasks use less quota, because Antigravity charges complex agent runs more. Or move part of the work to a different tool or a local model. None of these risk the Google account your email lives on.
References
Sources
Everything quoted in this post is from public pages. Quotas and policies change often, so check the official pages before relying on any number here.
Google Antigravity — Plans and rate limits
The official tiers, how quota is refreshed, AI credit overages, and the statement that usage limits are subject to modification.
https://antigravity.google/docs/plans/
Google — New Antigravity rate limits for Pro and Ultra (Dec 2025)
The change to five-hour refreshes for paid plans and a weekly limit for the free plan.
https://blog.google/feed/new-antigravity-rate-limits-pro-ultra-subsribers/
Gemini CLI — Addressing Antigravity Bans & Reinstating Access
Google's announcement of the ban cause, the reinstatement form, the usage-limits acknowledgement, and the permanent ban on a second violation.
https://github.com/google-gemini/gemini-cli/discussions/20632
Google AI Developers Forum — Hardware ID limits on multiple accounts
A user request to stop account rotation, with a moderator saying a feature request would be filed.
https://discuss.ai.google.dev/t/feature-request-google-should-limit-the-use-of-multiple-accounts-based-on-the-users-hardware-id-in-antigravity/128183
Cursor Forum — "Too many free trial accounts used on this machine"
Cursor's device-level trial limit, and how it misfires on shared networks.
https://forum.cursor.com/t/blocked-from-free-trial-due-to-company-vpn-public-ip-is-there-a-solution/115179
GIGAZINE — Google Gemini accounts banned over OpenClaw
Coverage of the February 2026 ban wave that hit paying Antigravity subscribers.
https://gigazine.net/gsc_news/en/20260224-google-gemini-openclaw-accounts-banned
Key takeaway
"Read the plan limits and the ban announcement before installing anything that promises to get around them."