Seeing antigravity CLI chats in remote control and vice versa

System & Environment:

  • Setup: Remote Linux machine accessed via SSH

  • Tools: antigravity-cli and antigravity-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

  1. 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?

  2. 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?

  3. 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?

Hi @pmandl ,

Could you please provide a few more details to reproduce this issue.

  • The Operating System you are using? (e.g. macOS, Ubuntu Linux, Windows 11 / WSL2)
  • The shell you are using? (e.g. bash, zsh, fish, PowerShell, cmd.exe)
  • The terminal you are using? (e.g. iTerm2, Kitty, Alacritty, WezTerm, Windows Terminal)
  • The runtime version you are using? (e.g. Node.js, Python, or CLI runtime version)
  • If possible, can you share the exact reproduction steps to reproduce this issue or screen recording?

Please also share your Antigravity CLI version (`antigravity --version`) and full terminal reproduction logs.