Antigravity v2.1.4 on Windows 11 shows blank screen / wrong local port after startup

[Yaswanth_Tummala]

Title: Antigravity v2.1.4 on Windows 11: GPU crash on normal launch, and blank UI / wrong local port after workaround flags

Environment

• App: Antigravity v2.1.4

• OS: Windows 11 Home 25H2 (Build 10.0.26200)

• Laptop: Dell Inspiron 15 3520

• GPU: Intel Iris Xe Graphics

• Updated graphics driver to: Intel Graphics Driver 32.0.101.7088

Problem summary
Antigravity does not open correctly on my Windows laptop.

Behavior without launch flags

Launching Antigravity normally causes Electron GPU-process failures and the app exits. The logs show messages like:

• GPU process exited unexpectedly

• GPU process isn't usable. Goodbye.

Behavior with workaround launch flags

If I launch Antigravity with:

"C:\Users\yasht\AppData\Local\Programs\antigravity\Antigravity.exe" --disable-gpu-sandbox --disable-gpu --use-angle=swiftshader

then the app no longer crashes immediately, but the Antigravity window is just a blank/black screen.

I also opened the local Antigravity URL in the browser and it is blank / fails as well.

---

Troubleshooting already attempted

I already tried the following:

1. Deleted/renamed %APPDATA%\Antigravity to clear Antigravity profile/cache

2. Deleted cache-related folders under the Antigravity profile

3. Tried --disable-gpu

4. Tried Electron/software-rendering environment variables

5. Updated Intel Iris Xe graphics driver to 32.0.101.7088

6. Rebooted after the driver update

7. Tested Antigravity again

The issue still persists.

---

Important logs / findings

language_server.log

The language server appears to start successfully and listen on:

• 51986 for HTTPS (gRPC)

• 51987 for HTTP

The log ends with successful initialization, e.g.:

• language server listening on random port at 51986 for HTTPS

• language server listening on random port at 51987 for HTTP

• initialized server successfully

main.log

main.log shows Antigravity auto-reloading the window to different local ports. In particular, I observed:

• first it used a local UI URL like:

  • https://127.0.0.1:53227/

• later it auto-reloaded the window to:

  • https://127.0.0.1:51986/

However, 51986 is the language server backend port according to language_server.log, not the frontend UI port.

This suggests Antigravity may be reloading the UI window to the language server gRPC port instead of the correct frontend app/UI port.

Browser / DevTools symptoms

When I opened the local page in the browser and checked DevTools, I saw errors such as:

• ERR_CONNECTION_REFUSED

• failed POST requests to:

  • /exa.language_server_pb.LanguageServerService/...

The browser page and Electron window both remain blank.

---

Suspected bug

It looks like there may be two related issues on Windows:

1. GPU-process crash on normal launch for this Electron build / environment

2. Incorrect window reload / routing to the language server port after using workaround flags, causing the frontend to stay blank

The most suspicious behavior is that the app reloads to https://127.0.0.1:51986/, even though that appears to be the language server backend port rather than the actual frontend UI port.

---

Request

Could you please check whether Antigravity v2.1.4 on Windows has:

• a GPU startup regression with Intel Iris Xe / Electron

• and/or a bug in the local auto-restart / port-routing logic that reloads the UI to the backend language-server port?

I can provide screenshots and the full main.log / language_server.log if needed.