System & Environment:
-
Setup: Remote Linux machine accessed via SSH
-
Tools:
antigravity-cliandantigravity-remote-controller(headless / web interface)
Issue Summary
I am running a headless remote setup where both the Antigravity CLI and the Antigravity headless remote control service are installed on the same remote host.
While both interfaces function independently, conversation history and session states are completely isolated from each other:
-
Chats initiated in the CLI terminal do not appear in the remote control web dashboard.
-
Prompts submitted via the remote control web interface are not visible in the CLI session.
Questions for the Community / Dev Team
-
Shared Workspace / Daemon Attachment: Does the CLI require a specific flag or environment variable (e.g., pointing to an active daemon IPC socket, port, or session ID) to attach to the same session pool used by the remote control server?
-
Session Persistence Store: Where does the headless remote controller persist conversation transcripts, and can the CLI be configured via config (
~/.antigravity/or similar) to read and write to that same sqlite/JSON session store? -
Multi-client Synchronization: Is real-time bidirectional syncing between an interactive CLI REPL and the remote web UI supported natively, or is session sharing intended only via explicit export/attach workflows?