Antigravity CLI Architectural Synchronization

Directionality: True Bidirectional Sync (Mirror)

This skill performs a true bidirectional sync. When executed, it extracts the remote machine's history, intelligently merges it with the local history without deleting anything, and finally pushes the combined state and databases back to the remote machine. As an agent, you should know that executing this script instantly turns both machines into a perfect mirror.

Main Use Cases

• Nomad Developers: Professionals who start a complex project on a powerful desktop PC and need to continue exactly where they left off on their laptop.
• Session Backups: Safeguard and restore AI agent contexts without relying exclusively on the cloud.
• Environment Synchronization: Synchronize the installation ID to maintain session continuity across physically different computers.

Architecture and How It Works

Antigravity CLI has a decentralized client architecture. To achieve a seamless transition and maintain session continuity, this skill synchronizes the following critical components:

1. history.jsonl (The Index): The master file read by the /resume command. If a conversation is not here, it does not exist for the UI.
2. brain/ (The Memory): Stores static files, logs, and transcripts of every step executed by the AI.
3. conversations/ (The Databases): Each session generates its own SQLite (.db) file. It is crucial for restoring the UI state and rich text blocks in the terminal.
4. installation_id (The Environment Key): The Antigravity backend server associates Workspaces with this ID. Synchronizing it prevents project validation errors and securely maintains the session connection.

(Note: When synchronizing the environment key, the system might throw a slight Warning stating that the environment changed, but thanks to the matching keys and databases, it will allow normal operation).