Antigravity updates IDE UI and resets weekly limits

• Google said the IDE in Antigravity 2.0 never disappeared, and OfficialLoganK's update says a UI change now makes that clearer.
• The same post from OfficialLoganK reset everyone's weekly limits, after earlier limit increases that OfficialLoganK's rate-limit post and OfficialLoganK's weekly-quota post described as 3x changes.
• Some of the frustration was timing: bennash's reply argued the clearer IDE marker landed after users had already spent hours adapting to the earlier rollout.
• Complaints were not just about UI. bennash's quota complaint and bennash's Genie example both focused on a shared quota that appeared to tie coding and media generation together.

You can read the UI clarification, compare it with the earlier rate-limit increase, and see how quickly the conversation shifted from missing-IDE complaints in bennash's post and another bennash post to quota complaints in bennash's later thread.

Google's clearest message was simple: the IDE was still there, the product just was not signaling it well enough.

That matters because a big slice of the backlash came from users who thought Antigravity 2.0 had replaced the old IDE workflow with an agent-first surface. bennash's complaint asked for the IDE back, while a repost of SiVola's criticism framed the launch as a full IDE-plus-agent replacement.

The rollout turned into a live quota revision. First, OfficialLoganK's post said Antigravity had tripled rate limits across all tiers. Hours later, another OfficialLoganK update said weekly quotas were also tripled.

By May 22, OfficialLoganK's follow-up said the team had reset everyone's weekly limits as part of the IDE-clarity update. a repost of the Google AI developers note described the higher Gemini limits on paid tiers as permanent, which suggests Google was still adjusting both messaging and capacity in public.

The sharpest criticism was not that Google changed course, but that it changed course after users had already burned time on the new setup.

According to bennash's post, a clearer UI cue at launch could have cut a substantial amount of the negative reaction. another bennash post also complained that Google had not directly addressed the backlash, even as product updates kept shipping through Logan Kilpatrick's account.

The most concrete downstream complaint was quota coupling. bennash's post said code generation and video generation now draw from one pool, and a follow-up example said that change made Google Genie less useful because every experiment consumed credits needed for coding.

The same thread widened that complaint beyond coding. bennash's MacOS Tahoe post reported app repaint issues, while a repost from nathanclark_ mocked how fragmented Google's access paths had become across Gemini, AI Studio, personal Google One accounts, and Workspace.