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.