Problem: Currently, Antigravity Remote Sessions only support cloud-hosted environments. For developers whose primary compute, GPUs, Docker containers, or codebases live on self-hosted Linux machines or private servers accessed via SSH, there is no way to register or attach a custom SSH host as a remote target in Antigravity.
Why this matters:
- Relying on local prompt workarounds (telling the agent to wrap commands in
ssh user@host ...) breaks on long trajectories and complex shell escaping. - Running Antigravity locally on a thin laptop while managing workloads on a personal SSH workstation/server is a very common workflow, and cloud-only remote sessions leave this gap uncovered.
Proposed Solution: Allow users to add custom SSH targets (e.g., via ~/.ssh/config or host/key configuration) in Antigravity Remote Sessions—bootstrapping a lightweight remote agent host over SSH so file edits, terminal commands, and sessions run natively on the user’s own SSH machine.