Issue Summary:
I’m unable to complete the login process in Antigravity on Windows. The OAuth authentication succeeds in the browser, but the callback redirect fails with missing parameters, preventing the application from receiving the authentication token.
Environment:
- OS: Windows 11
- Antigravity Version: Latest (downloaded from antigravity.google/download)
- Browser: Chrome (also tested with Edge)
- Google Account Region: Changed from Hong Kong to Singapore
- Network: Using system-level VPN (Singapore node)
Steps to Reproduce:
- Launch Antigravity application
- Click “Sign in with Google”
- Browser opens and redirects to Google OAuth page
- Successfully authenticate with Google account
- Browser shows “You have successfully authenticated” page
- Page attempts to redirect to
antigravity://oauth-success - Browser console shows: “Launched external handler for ‘antigravity://oauth-success’”
- Application does not receive the callback - login never completes
What I’ve Tried:
- Reinstalled Antigravity 2 times (complete uninstall + data cleanup)
- Tested with multiple browsers (Chrome, Edge)
- Cleared all browser cookies and cache
- Verified protocol handler is registered in Windows Registry (HKEY_CLASSES_ROOT\antigravity)
- Manually triggered protocol with
antigravity://oauth-success- no response - Changed Google account region from Hong Kong to Singapore
- Revoked all Google account permissions and re-authenticated
- Tested with and without VPN
- Cleared Antigravity application cache
- Ran application as Administrator
Registry Verification:
The protocol handler is correctly registered:
HKEY_CLASSES_ROOT\antigravity\shell\open\command
(Default) = "C:\Users\[username]\AppData\Local\Programs\Antigravity\Antigravity.exe" "--open-url" "--" "%1"
Browser Console Errors:
Launched external handler for 'antigravity://oauth-success'.
ERROR TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'.
Observations:
- The OAuth authentication itself succeeds (confirmed by “successfully authenticated” message)
- The issue is specifically with the callback redirect mechanism
- The protocol handler exists but the application doesn’t respond to the callback
- This appears to be a Windows-specific issue based on similar reports in the forum
Question:
Is this a known issue with Antigravity on Windows? Are there any workarounds or fixes available? Is there an alternative authentication method (such as API key) that can be used instead of OAuth?
Any help would be greatly appreciated!