Google Antigravity Lets Developers Run AI Agents on Remote Linux Servers Google released Antigravity v2.33.0, adding SSH host connections that let the desktop app run projects, agents, Git worktrees and terminals on a remote Linux server, with agents continuing to work after the local window closes, according to Google's release notes. Hosts must run 64-bit Linux with glibc 2.26+, and macOS, Windows and Alpine are not supported; developers connect via the sidebar, command palette or the --ssh-host flag using existing ~/.ssh/config entries. The same release added GitHub pull request status pills and in-page browser search, and SSH joins Remote Control and Remote Agents as Antigravity's third remote workflow. Google Antigravity Lets Developers Run AI Agents on Remote Linux Servers 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 https://antigravity.google/docs/ssh/?utm source=alphasignal 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-host flag, 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 https://antigravity.google/docs/remote-control/?utm source=alphasignal and Remote Agents as Antigravity's third way to work remotely. - The same release https://antigravity.google/docs/changelog/?utm source=alphasignal 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 https://antigravity.google/docs/changelog/?utm source=alphasignal , 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 https://antigravity.google/docs/ssh/?utm source=alphasignal . 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 https://antigravity.google/docs/remote-control/?utm source=alphasignal | 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=