Windows: Antigravity 2.27.0 and 2.28.0 stuck on Google sign-in — Login RPC remains Pending

Summary

Antigravity gets stuck indefinitely on the Google sign-in loading screen. Clicking “Sign in with Google” does not open any browser window or tab.

The issue occurs in both Antigravity 2.27.0 and 2.28.0 on Windows.

Steps to reproduce

  1. Launch Antigravity while signed out.

  2. Click “Sign in with Google”.

  3. The interface stays loading indefinitely.

  4. No Google authorization page opens.

Diagnostic findings

  • LanguageServerService/GetUserStatus returns HTTP 200.

  • LanguageServerService/Login remains Pending in Chrome DevTools Network.

  • The language_server.exe process starts a new local listening port after clicking the sign-in button.

  • The local /auth/callback endpoint returns HTTP 400 when called manually without OAuth state.

  • A test URL opened through window.open() in the Antigravity renderer successfully opens Chrome.

  • The language server log repeatedly reports: error getting token source: You are not logged into Antigravity.

  • The original application bundle contains https://daily-cloudcode-pa.googleapis.com.

  • Both the daily and production Google Cloud Code endpoints accept HTTPS connections. Unauthenticated POST requests to loadCodeAssist return HTTP 401.

  • No Windows proxy or HTTP_PROXY / HTTPS_PROXY variables are configured.

  • The issue persisted after testing versions 2.27.0 and 2.28.0 and resetting local application state.

  • Changing the Cloud Code endpoint did not resolve the issue. The original app.asar has been restored.

  • No BigInt serialization error was found in the available main.log.

Expected behavior

The language server should generate the Google OAuth authorization URL, open the browser, and complete the authentication flow.

Actual behavior

The local OAuth callback listener starts, but the Login RPC remains pending and no browser opens. The application never obtains an authenticated session.

Could the Antigravity team investigate whether the language server is failing to generate the OAuth authorization URL or terminating silently before returning it? Please advise on a supported diagnostic procedure or workaround for Windows.

Hi @IRVING_VALLE_GARCIA,

LanguageServerService/Login actually stays Pending on purpose—it doesn’t return the OAuth URL to the UI, it just waits until the local /auth/callback port gets the redirect from your browser. Since that local port started up and returned HTTP 400, language_server.exe has already generated the OAuth URL in memory.

The reason window.open() works in DevTools while the button doesn’t open Chrome is that language_server.exe launches the browser itself on Windows via %SYSTEMROOT%\System32\rundll32.exe url.dll,FileProtocolHandler <url>. If Defender/endpoint security blocks language_server.exe from spawning rundll32.exe, or if SYSTEMROOT is missing in its environment, the browser launch fails silently and Login waits forever.

As a quick workaround, close Antigravity and launch it from PowerShell with $env:ANTIGRAVITY_VSCODE_HOST="1" (redirecting output to a log file like & "$env:LOCALAPPDATA\Programs\Antigravity\Antigravity.exe" > "$env:TEMP\agy.log" 2>&1). When you click “Sign in with Google”, language_server.exe will skip rundll32.exe and print ANTIGRAVITY_OPEN_URL: https://accounts.google.com/... into that log file. Just copy and paste that URL into Chrome—once you sign in, it’ll hit the local callback port and log you right in. (If you have the agy CLI installed, signing in there also shares the same Windows Credential Manager token.)