Antigravity urgently needs a clearly separated Beta / Preview release channel before changes are pushed to regular users.
I am saying this based on direct experience, not theory.
In my case, updates broke one of the most important parts of the product: conversation continuity and project memory.
-
On older versions, some chat history could still be seen, but the product forced an update before it could be used properly.
-
On newer versions, even newly created chats may fail to load correctly after reopening.
-
When that happens, I have to explain the whole project to the agent again from the beginning.
For an AI IDE, this is not a minor inconvenience. This is a core workflow failure.
If chat continuity breaks, the product loses a major part of its value for real development work.
That is exactly why a proper Beta / Preview channel matters.
Users who are willing to accept instability should be able to test new builds first, report regressions early, and help catch serious issues before they reach stable users. Right now, it feels like regular users are carrying the risk that should have been absorbed by a testing channel.
A better release process would include:
-
a clearly separated Beta / Preview channel
-
a Stable channel for users who need reliability
-
visible known issues before broad rollout
-
a proper recovery path for chat history and project-memory failures
-
a safer rollback path when a release damages core workflows
Fast iteration is understandable. But for features like chat history, project context, and conversation persistence, reliability has to come first.
Please introduce a formal Beta / Preview program for Antigravity, so critical regressions can be found earlier instead of disrupting regular users after release.
thanks you.