Antigravity CLI and Antigravity 2.0 share the same core agent engine, which means a session you start in the terminal can continue in the full GUI application without losing context. If you begin work in the CLI and later need visual orchestration, richer project management, or a more comprehensive interface, you can export your session and pick up exactly where you left off.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/google-antigravity/antigravity-cli/llms.txt
Use this file to discover all available pages before exploring further.
When to export a session
The CLI is optimized for speed, keyboard efficiency, and remote workflows. The Antigravity 2.0 GUI is built for comprehensiveness — visual orchestration, heavier project management, and tasks where a rich graphical interface adds real value. You might want to export when:- A task grows in scope and you want visual tools to manage multiple workstreams.
- You need to hand off a session to a teammate who works primarily in the GUI.
- You want to review diffs, history, or agent steps in a more structured visual layout.
- You are moving from a remote server back to a local workstation.
Export your session
Finish your current turn
Wait for the agent to complete its current step before exporting. Exporting mid-turn is not recommended, as in-progress tool calls may not transfer cleanly.
Open the session export option
In the CLI, use the session export option to prepare your session for transfer to Antigravity 2.0. The CLI confirms the session is ready before initiating the transfer.
Open Antigravity 2.0
Launch the Antigravity 2.0 GUI on your local machine. If you exported from a remote server, make sure you are signed in with the same Google account on your local machine.
What carries over
Because both interfaces run on the same shared core agent engine, the following session data is preserved when you export:- Conversation history: Every message, agent response, and tool call from the CLI session.
- Session context: The agent’s understanding of your codebase, open files, and task state at the time of export.
- Permissions and settings: Tool permissions and preferences sync bidirectionally between the CLI and the GUI.
Antigravity CLI and Antigravity 2.0 run on the same core agent engine. This means improvements to the underlying agent apply to both interfaces simultaneously, and exporting a session does not change how the agent reasons or executes — the same engine continues running your task in the new interface.