Free to read for non-members here
Well, the “Agent-First” future is here, and it apparently thinks my code is trash (It might be, who knows?)
Look, here’s the thing,
an “Agentic Development Platform” that doesn’t just autocomplete code — it understands your project is still not convincing to me.
because
It was supposed to be “Mission Control” for AI agents that can plan, code, and browse the web to build your app for you, not delete things from your existing code and make it work in whatever way It wanted.
And yeah, I didn’t want a “Hello World” demo.
I wanted to see if Gemini 3 Pro in Antigravity could handle a real refactor.
The Setup:
I simply brought in all my settings from VS Code.
I opened my existing dashboard app in Antigravity. The Antigravity UI is fine, it looks like VS Code but with a “Manager View” where you supposedly orchestrate your AI minions.
I decided to start small.
There was a CSS layout issue on the settings page, yk like a misaligned flex container that was refusing to center.
I typed into the Agent Manager:
“Fix the vertical alignment in the Settings component.”
[If you tell me the prompt wasn’t up to the mark, I’ll just let you know It went to the right file, changed the right lines, but sucked :)]
Antigravity’s agent spun up. It generated a “Plan.” It looked confident.
Then it started editing.
Attempt 1: It changed display: flex to display: grid but forgot the row definitions.
Attempt 2: It reverted to flex but added position: absolute to the child elements. Now my buttons were floating on top of the navbar.
Attempt N:
When I tried to intervene and say, “No, just use align-items,” the agent argued with me. It entered a loop of “Verifying changes…” followed by “Reverting changes…” until it eventually just timed out with a “Model Quota Exceeded” error.
Eventually, I changed the model to Claude Sonnet 4.5
and It felt like the IDE and this model were chewing on my code rather than writing it.
The breaking point:
Eventually, It made the changes and I accepted it :)
The alignment was fixed. The Dashboard was gone :)
Status: Deleted, literally.
The “optimization” model had apparently decided that the most optimal way to render the dashboard was not to render it at all.
It treated the entire component as “dead code” and wiped it from existence.
The Verdict
Although It worked well with some of my basic scripts in Go and Python, it failed miserably here.
This is a fascinating glimpse into the future, but right now, it feels like giving a 5 y.o a chainsaw.
The “Agentic” workflow is impressive when it works, but terrifying when it fails.
If you’re going to try it, maybe stick to boilerplate apps for now.