Antigravity 2.0 Walkthrough https://youtu.be/6C0FjHoN3qE?si=sH0KAue5MC3mLUdM CLI Walkthrough https://youtu.be/am0lg5-ofvQ?si=tdUZVpHsotvL9YGj SDK First Look https://youtu.be/RGhunHLnVIg?si=QuBbBbT-C0g5-hRN Science Skills in Antigravity https://youtu.be/v0eokiSJO74?si=0ogkL_VsiwD8CnMz Marketers using Antigravity https://youtu.be/1rF_SZZ3yWs?si=DkX_F4WNBbPLGgfz Blog - https://antigravity.google/blog Changelog - https://antigravity.google/changelog

One of the features that Antigravity IDE 2.0 lost momentum on is the Browser subagent. The old Antigravity could seamlessly tap into my playwright script to use the Edge Browser as coded to run my workflows , it will launch and even show blue display that it's connected to the Browser of my choice. In 2.0, that's feature is gone (from my observation) . Although the Browser Subagent is now even visible to launch, it doesn't use my browser persistent code, rather launches the Isolated Chromium Browser. Now I can't override it anymore. The blue 💙 agent display feature, the Broswer subagent futuristic control of the browsers is deprecated. Now it's pure playwright cdp debug experience, I chose Antigravity over the rest specifically because of the initial Browser subagent experience. Now I don't see anything holding me onto the product anymore, I am just stuck onto it. What I do now is to write debug scripts and give my opened browser context for DOM interaction using playwright cdp. It's a lot of tokens usage

I loved Google Antigravity when it first launched, but after using it more, I feel the visible issues like errors, tokens, and bugs are only surface-level problems ( like it was on Windsurf XD) . The main issue for me is that the models often agrees too easily with the user and builds plans from limited context instead of deeply understanding the codebase, architecture, and real constraints. I really want to use Google’s own model inside Antigravity, not rely on other models, but right now it is not reliable enough for serious long tasks. Please focus less on side features and more on model quality, deep code comprehension, critical reasoning, and trustworthy execution.

As we transition from Antigravity v1 to v2, we seem to have encountered a slight, unexpected edge case: inertia ;p We knew upgrading the core levitation matrix while hurtling through production at terminal velocity would be a bit of a ride, but currently, the local spacetime fabric feels less like a smooth quantum glide and more like a gravel road in a 1998 Honda Civic with blown struts. For those currently experiencing intermittent gravitational anomalies, random kinetic reorientation, or coffee cups floating at a precise 45-degree angle, please note: It’s not a bug, it’s a feature: They are simply stress-testing Newton's First Law. (Spoiler: Newton is winning). The "Bump": Is actually just a localized temporal compression artifact. Or a caching issue. Let's go with caching. Pro Tip: Avoid sudden operational maneuvers until the sub-atomic deployment pipeline settles. If you feel weightless, please anchor yourself to the nearest stable monolith. We appreciate your patience while we recalibrate the localized Higgs field. Keep your eyes on the telemetry, your seatbelts securely fastened, and remember: what goes up doesn't technically have to come down if our code is solid. May the net force be ever in your favor.

The new range of usage limits just killed Antigravity. Unfortunately

I've not updated antigravity as I absolutely want to keep the IDE experience. I've spent months in structuring my workspaces, MCPs, git branches, AGENTS.md, ... Will I find everything back, including conversations history, would I finally update?

I absolutely love Antigravity! The implementation planning and the task MD artifacts are game-changers. I’ve actually optimized this system further to create a "scattered-brain" wrapper, which helped me build a full website with complete services and a Gemini-connected AI bot in no time. Huge thanks for building this amazing tool! If you’re looking for collaborators to improve the artifact system, I’ve built a pretty stable encapsulation layer that works wonders. Would love to share and collaborate!

"I love using Antigravity to close the gap on this IaC project, specifically for workspace migration. It provides AI-assisted support for SCC, SecOps, and Chronicle integration."