Antigravity ACP server in zed fails to start on remote Linux hosts using OS Login / NSS (Exit 255)

Google Antigravity
,
1

The Antigravity extension in Zed works fine locally on macOS, but fails when connecting to a remote Linux machine via Zed Remote Development. Opening the agent panel immediately fails with
Server exited with status exit status: 255

The Antigravity CLI (agy) works fine on the same machine.

Workaround

Adding the OS Login account to local /etc/passwd and /etc/group resolves the issue:

getent passwd $(id -u) | sudo tee -a /etc/passwd
getent group  $(id -g) | sudo tee -a /etc/group

Environment

  • Client: Zed 1.18.0 on macOS
  • Remote: GCE Debian 13 (x86_64), OS Login enabled
  • Agent build: agy_acp_server_20260818_01_RC01
2

Hi @Mz0001

To help us better assist you and investigate this issue, we need to understand exactly what is triggering this behavior on your end.

Could you please provide the specific, step-by-step flow you followed right before encountering the issue?

Alternatively, if it is possible, sharing a screen recording that captures your exact workflow and the resulting error would be incredibly helpful for our engineering team.

3
  • install zed locally on mac
  • install the antigravity extension in zed
  • remote into a GCP VM with OS login enabled using Zed’s “connect to ssh server”
  • open the agent panel
  • click the plus button at the top and click the antigravity button
  • >Server exited with status exit status: 255