Google's Antigravity 2.0 and the Gemini CLI 'Bait and Switch'

Google's release of Antigravity 2.0 highlights a deep friction between cutting-edge model capability and a hostile, "rug-pull" developer ecosystem. While Antigravity 2.0 (using Gemini 3.5 Flash High) topped the OpenSCAD Architectural 3D LLM Benchmark by successfully modeling the complex geometry of the Pantheon, developers are furious over the simultaneous announcement that the open-source "Gemini CLI" will be completely deactivated on June 18, 2026.

This transition forces developers to migrate to the closed-source, proprietary "Antigravity CLI." The move has sparked intense backlash due to a series of ecosystem degradations:

• Authentication Friction: The new CLI forces browser-based logins that fail on systems like WSL because of OS-level keyring (dbus) integration issues.
• Protocol Gaps: Antigravity CLI lacks support for the open Agent Client Protocol (ACP), which developers rely on to build flexible, multi-agent workflows.
• Retroactive Quota Cuts: Users on "AI Pro" subscriptions report that Google retroactively slashed their token limits overnight, locking them out of their workspaces for up to 7 days without warning.

The community is deeply split. While some praise the sheer intelligence and spatial reasoning of the new models, most developers express resentment over Google's classic "bait and switch" playbook—releasing open-source tools to build an ecosystem, only to kill them in favor of proprietary, metered, and unstable closed-source alternatives.

"If it's ok I'd prefer they just work on reaching a baseline acceptable rollout before worrying about being Top in anything." — Comment by mellosouls

"I really hate having a service I think I'm paying for rug-pulled with no clear justification." — Comment by leoedin

"Say goodbye to metered usage via API keys you control, and hello to opaque pricing and usage limits." — Comment by mpalmer