Right now it is unclear whether conversations are going to be retained when I login in a new device with the same login. Push conversations to cloud.
Antigravity needs to give the Google experience, every IDE will eventually end up with same set of features, ecosystem is going to make the difference and Antigravity needs to start supporting it early.
Hi @amrish
Thank you for your feedback. We appreciate you taking the time to share your thoughts with us, and we’ll be filing a feature request.
Building on @amrish point, retaining conversation history is merely a baseline. To deliver a functional cloud experience, Antigravity must implement full workspace and runtime persistence, leveraging the infrastructure models already established by Firebase Studio and Jules.
When authenticating on a new device, the AI agent requires immediate access to the active execution context, not just the text ledger. For instance, when debugging a Python application with isolated virtual environment dependencies or analyzing a TypeScript architecture with strict configurations, the containerized state, environment variables, and active language server contexts must persist in the cloud.
Jules currently demonstrates this capability by spinning up remote VMs to execute tasks and maintain state. Antigravity needs to integrate a similar architecture, syncing the runtime container state alongside the conversation history. This ensures the AI maintains unbroken contextual awareness of the execution state and local dependency graphs across all client instances.
Furthermore, transitioning agentic task execution from local hardware to cloud infrastructure is essential for resource efficiency. Running autonomous, multi-step agents locally severely bottlenecks performance on standard hardware. By delegating heavy compute and language server operations to remote instances, Antigravity would decouple IDE performance from client specifications, making the platform fully viable on low-resource hardware such as Chromebooks.