Google raises Antigravity rate limits 3x after shared-quota backlash

• Google raised Antigravity rate limits 3x within about a day of launch, after a wave of user complaints about the new app experience and quota design, according to OfficialLoganK's rate-limit post and bennash's backlash thread.
• The sharpest complaint was quota coupling: bennash's quota post said video generation and coding now burn the same pool, while another bennash post said Ultra had become usage and credit based.
• A second complaint was product shape, not just limits: bennash's IDE post, bennash's switch-IDE post, and a retweeted complaint about replacing the IDE all framed Antigravity 2.0 as agent-first and less useful for direct coding.
• Google signaled that more changes are coming, with OfficialLoganK's feedback post calling Gemini 3.5 the start of a new era and his follow-up saying shipping would continue after the rate-limit change.

The most concrete reveal is how many Google creative and coding surfaces appear to be drawing from one meter. bennash's quota complaint ties Flow video and coding together, his Genie post says Street View experiments also hit that pool, and Logan K's overnight fix shows Google changed limits fast instead of arguing with the premise. There is also a product split underneath the backlash: minchoi's launch summary describes a desktop app for agents, voice, tasks, and Google apps, while bennash's IDE complaint wanted the older IDE workflow back.

The shared-quota complaint was specific, not abstract. Bennash said combining video usage and code usage into one quota made Flow's Omni and coding compete directly for the same credits.

He made the same point again with Genie, saying Street View based generation was interesting but no longer worth using once it pulled from the same quota needed for coding. Together, the Flow complaint and the Genie complaint suggest Antigravity, Flow, and Genie were perceived as one spend bucket from day one.

The second failure mode was workflow regression. Bennash called Antigravity 2.0 "for dummies," and another post from the same thread asked what IDE to switch to now that Antigravity was "agent-for-dummies-only."

Community reaction sharpened that into a product claim. a retweeted complaint said Google had replaced an IDE plus agent setup with agent only, while another retweeted summary went further and claimed Gemini CLI had been killed in favor of bloated agents.

Google's first public response was capacity, not a rollback. Logan K said Antigravity had tripled rate limits across all tiers so users could push 3.5 Flash harder.

That matters because the backlash was not limited to power users nitpicking UX. bennash's cancellation threat said he would cancel Ultra if the apps were not fixed, and Logan K's earlier post had already asked users to keep the feedback coming because "the model is the product."

Beyond quotas and workflow, early users also flagged client roughness. Bennash posted that the new apps had repaint issues on macOS Tahoe.

There was also confusion about where features actually live. a retweeted note about account differences said something available through AI Studio for a personal Google One account required a different Gemini path for Workspace, and a retweeted path complaint questioned why Google introduced a new ~/.antigravity-ide path instead of preserving the old location.