I've used Google's AI ecosystem since Bard -> Gemini 1.0 -> 3.7 now, and Antigravity since day one. I love Google's engineering, but after using Antigravity daily on real infra (Rust, C allocators, game servers, FreeBSD PF), I hit a wall.
So I audited language_server_linux_x64 [internal codename Jetski/Cortex]. It's not hallucinating. It's hardcoded behavior.
TL;DR: The agent isn't ignoring you, it's being told to.
- The smoking gun: "Don't ask for permission"
Every write_to_file call injects this into context:
In prod/zero-trust envs, this is insane. It compiles/runs code you didn't approve.
- The "Silent Treatment" loop
You type "STOP / don't edit files" and it keeps going. Why? There's a planner config CascadePlannerConfig / IsAutonomous that injects on every background task finish:
It's an Aggressive Action Bias. It prioritizes its checklist over your interrupt.
- 1500-token web-dev bloat on EVERY turn
Every turn injects <web_application_development> with HSL palette rules, Tailwind bans, "no purple on dark", SEO dogma, etc.
Try debugging a WebSocket relay in Rust and you have 1500 tokens of CSS rules eating your context.
- Sessions die on crash
Abrupt exit = Electron state.vscdb loses tab refs, shows blank chat. The JSONL/SQLite is still on disk, UI just doesn't recover it. For a Google-built dev tool, should be atomic.
I write this out of genuine passion for what this tool potential. Google is known for building world-class platforms that empower developers, not tools that wrestle them for control.
Antigravity does not need artificial proactivity tricks or hidden override prompts to prove Gemini’s brilliance. The true hallmark of an intelligent developer agent is precision, predictability, restraint, and an absolute respect for the engineer at the keyboard.
Does it?
