Inter-office memo
- To
- Everyone on Google Antigravity
- From
- Mo, Chief Executive
- Date
- November 18, 2026, 9:13 AM CST
- Re
- SSH in the Antigravity App
Antigravity’s app now connects to Linux machines over SSH. How to set it up
On November 17, 2026, Antigravity App 2.33.0 added SSH. Choose Connect to SSH Host... and it installs its server on a remote 64-bit Linux machine using your ~/.ssh/config, so projects, Git worktrees, agents and terminals run there and keep working after you close the window. The changelog doesn’t limit it to a plan, and updates take a few days to reach everyone.
What changed on November 17
Antigravity’s changelog lists version 2.33.0 of the Antigravity App on November 17, 2026, under the headline “Connect over SSH and GitHub pull request integration.” Its first item reads:
You can now connect the Antigravity App to a remote 64-bit Linux machine over SSH from the sidebar, the project menu (SSH Host…), or the command palette (Connect to SSH Host…). Antigravity installs its remote server automatically over OpenSSH using your ~/.ssh/config so projects, Git worktrees, agents, and terminals run on the host and keep working even after you close the window.
So the agent works where your code lives. Its commands, builds and tests run on the other machine, with that machine’s files, toolchain and hardware, and your laptop is only the window.
The same release adds live status pills for GitHub pull request links and a Pull Requests section in the Overview panel, brings Cmd/Ctrl+F search to the built-in browser, and opens /swarm and UI plugin panels to business and enterprise accounts. If you don’t see the SSH option yet, the changelog explains why that can happen: “New versions roll out gradually and may take a few days to reach all users.”
Why it took six months
Antigravity 2.0 arrived on May 19, 2026, with the agent app as the main product. The editor became a separate download, the Antigravity IDE, whose changelog lists its “First release” the same day, and the app had no SSH option.
The complaints started the same day. “How should I remote into my GPU rig and continue my development there?” asked the thread on Google’s developer forum that collected them. It has 20 posts, the last on October 23, and more than 6,500 views, and none of the posts is from Google. “The agents window doesn’t support ssh,” one user wrote on May 20. On August 20, another asked: “Can someone from the developer team confirm this is in the works?”
People built their own ways around it:
- The standalone Antigravity IDE, whose own SSH connection works, users on the forum say, though not from the agent app.
- Google’s extension for VS Code, whose 1.0.0 release on August 18 added “Remote-SSH workspace support,” through VS Code’s Remote-SSH.
- Mounting the server’s files locally over SMB and running commands over SSH, as the community project agent-remote-workspace does.
- Telling the agent in AGENTS.md to wrap every command in
ssh, which one poster warned “inevitably breaks down in long, complex trajectories.”
On November 17, the day 2.33.0 came out, a user filed a feature request for custom SSH hosts, writing that “Running Antigravity locally on a thin laptop while managing workloads on a personal SSH workstation/server is a very common workflow.”
How to connect
-
Update the Antigravity App to 2.33.0 or later. If the update hasn’t reached you, wait a few days and check again.
-
Give the machine an entry in
~/.ssh/config, since that’s what Antigravity reads. A standard OpenSSH entry looks like this:Host gpu-rig HostName 192.168.1.50 User you IdentityFile ~/.ssh/id_ed25519Run
ssh gpu-rigin a terminal first, to be sure the connection works before Antigravity tries it. The machine has to be 64-bit Linux. -
Connect from the sidebar, from SSH Host… in the project menu, or with Connect to SSH Host… in the command palette.
-
Let Antigravity install its server on the host. From then on, that connection’s projects, Git worktrees, agents and terminals run there.
Before you hand an agent a server you care about, check its permission settings, because the commands it runs now land on that machine.
SSH, Remote Control or remote agents
Here is how SSH compares with Antigravity’s other remote and Linux options:
| Way | Where the work runs | Who can use it | Best for |
|---|---|---|---|
| SSH host, app 2.33.0 | Your 64-bit Linux machine | No plan limit in the changelog | A server, GPU rig or VM you reach over SSH |
| Remote Control | Your own computer, which must stay “powered on and online” | Google AI Pro and up, by the pricing page | Steering your computer’s sessions from a browser |
| Remote agents | “An isolated, Google-managed remote environment” | Google AI Pro or Ultra, on a personal account | GitHub repositories, with your laptop off |
| WSL, app 2.16.0 | A WSL distribution on your Windows PC | No plan limit in the changelog | Linux tools on a Windows computer |
| Antigravity CLI, over SSH | Wherever you run agy |
Every plan includes the CLI | A terminal session, kept alive in tmux |
The CLI already works over SSH. Its install guide says that “When running over SSH, the CLI detects the remote connection environment” and prints a sign-in link to open on your own computer, then asks for the code the browser shows. What 2.33.0 adds is the app itself: its projects, Git worktrees, agents and terminals, running on the other machine.
Remote agents are the choice when your computer will be off, but they work on “GitHub repositories, Google Drive files, and uploaded files,” not on your own machine. SSH is the choice when the work needs the server itself.
Update even if you won’t use SSH
2.33.0 lists 21 fixes, and three are worth having on their own. It fixes an issue “where the desktop app opened a local debug port on startup,” without saying what could reach it. It fixes one “where configured MCP headers were sent across cross-origin redirects,” which matters if you put a token in an MCP server’s headers. And it fixes one “where hooks or wildcard rules could bypass enforced command or outside-project file review.”
It also stops the app signing you out when you open it offline or hit “a temporary network failure,” and stops timed-out Git status checks on Windows from leaving background git.exe processes “consuming gigabytes of memory.”
If you’ve been using a workaround
- The standalone IDE or VS Code over Remote-SSH: keep it if you want an editor on the server. Google still updates the IDE; its version 2.7.0 came out on November 12. The app’s SSH is for the agent app’s projects and conversations.
- Mounted folders and SSH command runners: try one project over the app’s SSH connection before your next long run, and keep the old setup until the new one works on your machine.
- An AGENTS.md rule to run commands over
ssh: drop it from projects you open over the app’s connection, whose terminals already run on the host.
What Google hasn’t said
- There’s no docs page. On November 18, the contents of Antigravity’s documentation listed no page about SSH connections; the changelog entry is all there is.
- Which plans get it. The changelog names none, and the pricing page doesn’t mention SSH.
- Which hosts count. Google says “64-bit Linux,” without saying whether that includes ARM machines. macOS and Windows hosts aren’t mentioned.
- What happens when your computer sleeps. Work keeps going “even after you close the window,” Google says, but not whether it does when your own computer sleeps or loses its connection.
- Whether SSH conversations appear elsewhere, such as in Remote Control or on antigravity.google.com.
Antigravity in Enjoy
Enjoy runs Antigravity on the computer Enjoy is on, through the server Google offers apps such as Zed and JetBrains IDEs, so it doesn’t use the app’s SSH connections. It can run agents on another computer, such as a Mac mini or a Linux desktop, if that computer has the Enjoy app: Antigravity, Claude Code and Codex there each use their own plan, and you work with them from your main computer, your phone or a browser. Each computer beyond the first has its own monthly price (pricing). For a server you only reach over SSH, Google’s app is now the simpler route.
We’ll update this memo when Google documents SSH connections, or says who can use them.
9.Questions.
Can Antigravity connect to a remote server over SSH?
- Yes, since the Antigravity App’s version 2.33.0 on November 17, 2026. It connects to a remote 64-bit Linux machine from the sidebar, the project menu’s SSH Host... or Connect to SSH Host... in the command palette, installs its server there over OpenSSH using your ~/.ssh/config, and runs your projects, Git worktrees, agents and terminals on that machine.
Why don’t I see Connect to SSH Host in Antigravity?
- Most likely the update hasn’t reached you yet. Google’s changelog says “New versions roll out gradually and may take a few days to reach all users,” and the option arrived in the Antigravity App’s version 2.33.0. The machine you connect to also has to run 64-bit Linux.
Is SSH in Antigravity free?
- As far as Google’s pages say, yes. The changelog doesn’t limit SSH connections to any plan, and Antigravity’s pricing page doesn’t mention them. Remote Control is listed from Google AI Pro up, and remote agents need Google AI Pro or Ultra on a personal account.
Can I connect Antigravity to a Mac or Windows machine over SSH?
- Not by Google’s description, which is “a remote 64-bit Linux machine.” On a Windows PC, the app has connected to a local WSL distribution since version 2.16.0, and for a Mac you leave running, Remote Control lets you work with its sessions from a browser on Google AI Pro and up.
Do agents keep running on the server when I close Antigravity?
- Yes, by Google’s changelog. Projects, Git worktrees, agents and terminals “run on the host and keep working even after you close the window.” Google doesn’t say what happens if your own computer goes to sleep or offline instead.
How is SSH different from Antigravity’s remote agents?
- SSH runs the work on your own Linux machine, with its files, tools and hardware. Remote agents run in “an isolated, Google-managed remote environment” on GitHub repositories, Drive files or uploads, need Google AI Pro or Ultra on a personal account, and keep going with your laptop asleep.