Antigravity ACP Google authentication hangs in Zed over SSH instead of supporting remote OAuth or reusing existing CLI credentials

Google Antigravity
1

There is a bug in Antigravity ACP authentication when Zed is connected to a remote machine over SSH.

The Antigravity CLI is already authenticated on the remote machine and works correctly, including non-interactive commands. However, Antigravity ACP does not reuse those credentials. When oauth-personal is selected, it reaches:

Credentials missing or invalid. Launching browser login flow...

and then hangs indefinitely because the ACP process is running remotely over SSH.

The ACP should either:

  1. Reuse the existing authenticated Antigravity CLI session, or

  2. Support a headless/manual Google OAuth flow over SSH, as the CLI does.

Requiring an API key is not an equivalent solution for users who are paying for Antigravity access through their Google account.

This currently prevents Google-account authentication from working with Antigravity ACP in Zed over SSH.