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

Google Antigravity
,
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.