The latest Antigravity (2.0.1) made a lot of changes. The biggest for me , was splitting the single antigravity into a standalone agent manager (now just called “Antigravity”) and the Antigravity IDE. Thats fine.
The install was a disaster, Antigravity (ie the artist formerly known as “agent manager”) hijacked the IDE executable and it wasa impossible to get the IDE to run at all.. it kept popping open Antigravity. Well after a lot of messing around I fixed that. That’s fine too.
WSL integration was broken, it kept accessing it from windows filesystem. And all my conversation and workspaces were lost. I was able to kind of get them back. And I got WSL integration going in the IDE. So thats fine too … now.
BUT now WSL does not work in Antigravity. (just in the IDE). And the meagre effort of getting thngs working 100% blew through all my tokens. I had to wait 5 hours or so. It seems like a lot of bugs and a disaster, but there is no word from Google at all about it. Are they working on it? Did we really lose all our tokens? Will “Antigravity” support WSL properly again? So its not fine. I have work to do. I don’t know if I should wait for 2.0.2 or just do what everyone else I know does and use Claude.
No chance. Why would I invest $100 in a product when the basic plan is horrible. Usually a person would upgrade if they are satisfied with their experience, and trust the provider. If i get a bad service, why should I continue doing business with them AND pay them more? makes no sense.
It’s just a joke. The catch is that on Gemini I still see a cost of $200, and the information there states a limit 20 times higher than on Pro. On Google, however, the cost for Ultra is $100, but the description mentions a limit 5 times higher. Logically and mathematically speaking, the limit should be 10 times higher. We’ll have to learn from this ourselves.
I don’t think google aims to actually give developers tools to truly build.
Also they are heading in the direction of extremely user-friendly interface, so regular people can develop. But we as real developers want control, and accuracy.
Such a horrible installation experience all in all… no WSL support, if you install it inside WSL, it will not authenticate, the IDE gets replaced by the Agent manager, upgrading the IDE actually removed the whole app…
My guess is that they raced it out to meet the Google I/O conference date. We’re all devs, so I can sympathise with a release gone wrong. But not the dead silence about it …
Same, I think I’ll switch soon to Cursor, at least they tell you that by paying $20 you get $20 in AI credits with tons of models to choose from (and their price). It’s not like they suddenly eliminate your most used model or change the limits randomly based on your feelings.
Well after a long discussion with Antigravity itself, it confirmed what I suspected. It does not support WSL. The IDE does. Here is what it summarised from our conversation:
The Problem: In Antigravity 2.0, the Agent Manager (Companion App) was decoupled from the editor. It runs on Windows and lacks native WSL/remote capabilities, meaning it fails if projects are configured with WSL remote URIs (vscode-remote://wsl+Ubuntu/...).
The Conflict: You cannot rely solely on the IDE’s built-in chat because you lose the Companion App’s ability to run multiple parallel sessions, coordinate workspaces, and view conversation history.
The Hybrid Solution: We keep the project paths pointing to the Windows network share (\\wsl.localhost\Ubuntu\...) so the Companion App can find the files. When running terminal tasks, the agent automatically executes them inside Linux using wsl -d Ubuntu -e <command>.
--
Well it said a lot of other things too, that I had to point out were incorrect. So maybe it just tried to make me happy (It did not). But I think thats it. It just accesses the file system from windows, and run commands with the “wsl -d Ubuntu -e” prefix.
