Antigravity Agent (WSL) launches Windows-Host Chrome but fails to establish CDP connection

Google Antigravity
,
1

Hi Team,

I am reporting a blocking issue with the Browser Agent running in a WSL2 environment.

Diagnosis:

  1. Setup: Antigravity IDE running in WSL2 (Ubuntu).

  2. Action: Agent launches the browser.

  3. Observation: The browser opens successfully on the Windows Host side. The “Antigravity Browser Control” extension page loads (see attached screenshot).

  4. The Failure: The Agent hangs immediately after launch and cannot drive the browser (no navigation, no clicking).

Crucial Debugging Detail: I verified the process location using ps aux | grep chrome inside the WSL terminal. The result was empty. This confirms the browser is running as a Windows process, not a Linux/WSLg process.

Hypothesis: The Agent (inside WSL) is unable to reach the Chrome DevTools Protocol port on the Windows host due to WSL2 networking isolation or firewall rules blocking the callback.

Request: Does Antigravity require a specific manual port forwarding rule (e.g., netsh interface portproxy) or a specific .env configuration to allow the WSL-based agent to communicate with the Windows-hosted Chrome instance?

Environment:

  • OS: Windows 11

  • WSL: Ubuntu

  • Browser: Chrome (Windows Native)

Thanks.

2

Hi @Lior_Parente ,

Welcome to AI Forum!
Thank you for reporting this issue.

This is the same core problem described and solution provided in this thread. The issue is that the CDP port (9222) is being reserved or blocked by Windows internal services (specifically WinNat), which prevents the WSL-based agent from connecting to the Windows Chrome process.

To fix this on your Windows host (Run as Administrator):

  1. Check for reserved ranges: Run netsh int ipv4 show excludedportrange tcp in a terminal.
  2. Release the port: If port 9222 is within a blocked range, run net stop winnat to release it.
  3. Restore networking: After the agent successfully connects, you can restart the service with net start winnat.

Once the port is unblocked, the agent should be able to establish the connection and navigate as expected.

Please let us know if this resolves the problem or if the issue still persists.

3

@Lior_Parente I found this article on medium I hope it helps.

4

Hi Thatipamula and Chauhan-Pratham,

Thank you for the follow-up and for sharing those resources.

I wanted to let you know that this is no longer an issue for me as I have switched to using macOS. The problem is now resolved on my end.

Best regards,

Lior Parente