Google's Antigravity desktop app can now open a remote Linux machine over SSH, so agents, terminals and Git worktrees run on the server and keep going after you close the window.
- Google's Antigravity app now connects to remote Linux servers over SSH, starting in v2.33.0.
- Projects, agents, Git worktrees and terminals run on the host, and agents keep working after the window closes.
- You connect from the sidebar, the command palette, or the
--ssh-hostflag, using your existing~/.ssh/config. - Hosts must run 64-bit Linux with glibc 2.26+. macOS, Windows and Alpine aren't supported.
- SSH joins Remote Control and Remote Agents as Antigravity's third way to work remotely.
- The same release also added GitHub pull request status pills and in-page browser search.
Google Antigravity’s desktop app can now connect directly to remote Linux machines. Version 2.33.0 adds SSH host connections, according to the release notes, allowing the local app to manage projects and agents running on a server.
The desktop app provides the interface while the remote host handles the workload. Project workspaces, agents, Git worktrees, and terminals all live on the host, as described in Google’s SSH documentation.
Remote Linux replaces custom workarounds #
Developers using lightweight laptops previously had to assemble their own remote setups for heavy builds, Docker workloads, and large test suites. One developer on Google’s forum mounted server files over SMB and routed commands through a custom Model Context Protocol gateway over SSH because Antigravity’s desktop Agent Manager was confined to local workspaces.
The new connection flow removes those extra layers, but its target remains limited to Linux. Community attempts to connect to Windows hosts failed because Antigravity expects a supported Linux environment on the remote side.
Choose where agents run #
Antigravity now offers three remote workflows, distinguished by where the agent runs and how the developer connects:
| Option | Agent location | Connection | Best fit |
|---|---|---|---|
| SSH host | Your Linux server | Desktop app over OpenSSH | GPU systems, development VMs, and powerful workstations |
| Remote Control | A machine running the Antigravity app or CLI | Web browser | Accessing an existing session from another computer or phone |
| Remote Agents | An isolated Google-hosted virtual machine | Antigravity’s cloud service | Working from GitHub repositories, Drive files, or uploads without managing a host |
SSH hosts require no manual Antigravity installation on the server. The desktop app deploys and manages the necessary components through OpenSSH.
Connect with existing OpenSSH settings #
Developers can start a connection from the sidebar, the project menu’s SSH Host... command, or the command palette’s Connect to SSH Host... command. The app also accepts a launch argument:
--ssh-host=<destination>
Antigravity reads entries from ~/.ssh/config and displays them in its host picker. A configuration using a key and jump host could look like this:
Host devbox
HostName 203.0.113.10
User alice
IdentityFile ~/.ssh/id_ed25519
ProxyJump jump.example.com
The connection reuses OpenSSH keys, ssh-agent, and ProxyJump settings. On macOS and Linux clients, host-key checks, key passphrases, and two-factor authentication prompts appear inside the app.
Account authentication uses a browser-based OAuth flow, which redirects the developer to a browser for authorization. Supported account types include personal Google Accounts, Google Workspace, Pay As You Go, and Gemini Enterprise.
Agents keep running after disconnection #
Closing an SSH window disconnects the app while leaving active agents running on the server. They remain available until the developer reconnects or invokes Stop SSH Server....
Network interruptions and laptop sleep also trigger reconnection attempts. When the connection returns, the app reattaches to agents that are still running, allowing long refactors and test jobs to continue without an active laptop session.
Remote configuration comes from the server’s ~/.gemini/ directory. Skills, rules, hooks, MCP servers, and plugins load there, while Antigravity’s Linux terminal sandbox also runs on the remote host.
Check the host before connecting #
- Operating system: 64-bit Linux on x86_64 or arm64 with glibc 2.26 or newer. Examples include Ubuntu 18.04+, Debian 10+, and RHEL 8+.
- Unsupported systems: macOS, Windows, and musl-based Linux distributions such as Alpine. Many slim Docker images therefore cannot serve as hosts.
- SSH configuration: TCP forwarding must be enabled with
AllowTcpForwarding yeson the target and any jump hosts. - Network access: The server needs outbound HTTPS connectivity.
- Filesystem access: The account needs a
$HOMEdirectory where Antigravity can write and execute files. - Local client: Antigravity App 2.33.0 or newer on macOS, Windows, or Linux, plus OpenSSH.
An SSH window changes several local features. The built-in browser panel is hidden, /browser connects to Chrome on the remote host, and camera and screen access remain disabled.
The standalone Antigravity IDE is a separate product. Its documentation does not currently describe SSH host support, and community testers report that the feature is unavailable there.
Who benefits from the upgrade #
Google’s documentation lists no separate SSH fee, although developers still supply and pay for the remote Linux machine. Teams already maintaining GPU servers, development VMs, or shared workstations can now connect those systems without synchronizing code manually or maintaining SMB and SSH gateways.
Version 2.33.0 also adds in-page Cmd/Ctrl+F search to the built-in browser and status indicators for GitHub pull requests. SSH support remains the larger workflow change for developers whose builds and agents have outgrown their local machines.